one DEBUG_INFO is enough for everyone

@@ -136,26 +136,15 @@
 config DEBUG_INFO
 	bool "Compile the kernel with debug info"
 	depends on DEBUG_KERNEL
 	help
           If you say Y here the resulting kernel image will include
 	  debugging info resulting in a larger kernel image.
-	  Say Y here only if you plan to use gdb to debug the kernel.
-	  If you don't debug the kernel, you can say N.
+	  Say Y here only if you plan to debug the kernel.
 
-config DEBUG_INFO
-	bool "Enable kernel debugging symbols"
-	depends on DEBUG_KERNEL && USERMODE
-	help
-	  When this is enabled, the User-Mode Linux binary will include
-	  debugging symbols.  This enlarges the binary by a few megabytes,
-	  but aids in tracking down kernel problems in UML.  It is required
-	  if you intend to do any kernel development.
-
-	  If you're truly short on disk space or don't expect to report any
-	  bugs back to the UML developers, say N, otherwise say Y.
+	  If unsure, say N.
 
 config DEBUG_IOREMAP
 	bool "Enable ioremap() debugging"
 	depends on DEBUG_KERNEL && PARISC
 	help
 	  Enabling this option will cause the kernel to distinguish between

@@ -61,17 +61,12 @@
 	default 4
 	help
 	  This is the irq for the debug port.  If everything is working
 	  correctly and the kernel has interrupts on a control C to the
 	  port should cause a break into the kernel debug stub.
 
-config DEBUG_INFO
-	bool
-	depends on KGDB
-	default y
-
 config KGDB_MORE
 	bool "Add any additional compile options"
 	depends on KGDB
 	default n
 	help
 	  Saying yes here turns on the ability to enter additional

@@ -44,21 +44,12 @@
 	  printed when the kernel detects an internal error. This debugging
 	  information is useful to kernel hackers when tracking down problems,
 	  but mostly meaningless to other people. It's safe to say Y unless
 	  you are concerned with the code size or don't want to see these
 	  messages.
 
-config DEBUG_INFO
-	bool "Include GDB debugging information in kernel binary"
-	help
-	  Say Y here to include source-level debugging information in the
-	  `vmlinux' binary image. This is handy if you want to use gdb or
-	  addr2line to debug the kernel. It has no impact on the in-memory
-	  footprint of the running kernel but it can increase the amount of
-	  time and disk space needed for compilation of the kernel. If in
-	  doubt say N.
 
 # These options are only for real kernel hackers who want to get their hands dirty.
 config DEBUG_LL
 	bool "Kernel low-level debugging functions"
 	depends on DEBUG_KERNEL
 	help

@@ -35,22 +35,12 @@
 	  printed when the kernel detects an internal error. This debugging
 	  information is useful to kernel hackers when tracking down problems,
 	  but mostly meaningless to other people. It's safe to say Y unless
 	  you are concerned with the code size or don't want to see these
 	  messages.
 
-config DEBUG_INFO
-	bool "Include GDB debugging information in kernel binary"
-	help
-	  Say Y here to include source-level debugging information in the
-	  `vmlinux' binary image. This is handy if you want to use gdb or
-	  addr2line to debug the kernel. It has no impact on the in-memory
-	  footprint of the running kernel but it can increase the amount of
-	  time and disk space needed for compilation of the kernel. If in
-	  doubt say N.
-
 # These options are only for real kernel hackers who want to get their hands dirty.
 config DEBUG_LL
 	bool "Kernel low-level debugging functions"
 	depends on DEBUG_KERNEL
 	help
 	  Say Y here to include definitions of printascii, printchar, printhex

@@ -62,17 +62,12 @@
 	default 4
 	help
 	  This is the irq for the debug port.  If everything is working
 	  correctly and the kernel has interrupts on a control C to the
 	  port should cause a break into the kernel debug stub.
 
-config DEBUG_INFO
-	bool
-	depends on KGDB
-	default y
-
 config KGDB_MORE
 	bool "Add any additional compile options"
 	depends on KGDB
 	default n
 	help
 	  Saying yes here turns on the ability to enter additional