[-mm patch] DEBUG_SHIRQ should depend on DEBUG_KERNEL

[Adrian Bunk <bunk@stusta.de>]

DEBUG_SHIRQ is clearly a debugging option.

While moving the option below DEBUG_KERNEL, I also adjusted the help 
text to be completely visible in "make menuconfig" with a 80 char
width.

Signed-off-by: Adrian Bunk <bunk@stusta.de>

---

 lib/Kconfig.debug |   18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

--- linux-2.6.18-rc1-mm1-full/lib/Kconfig.debug.old	2006-07-13 21:52:55.000000000 +0200
+++ linux-2.6.18-rc1-mm1-full/lib/Kconfig.debug	2006-07-13 21:55:52.000000000 +0200
@@ -46,21 +46,21 @@
 	  you really need it, and what the merge plan to the mainline kernel for
 	  your module is.
 
-config DEBUG_SHIRQ
-       bool "Debug shared IRQ handlers"
-       depends on GENERIC_HARDIRQS
-       help
-         Enable this to generate a spurious interrupt as soon as a shared interrupt
-	 handler is registered, and just before one is deregistered. Drivers ought
-	 to be able to handle interrupts coming in at those points; some don't and
-	 need to be caught.
-
 config DEBUG_KERNEL
 	bool "Kernel debugging"
 	help
 	  Say Y here if you are developing drivers or trying to debug and
 	  identify kernel problems.
 
+config DEBUG_SHIRQ
+	bool "Debug shared IRQ handlers"
+	depends on DEBUG_KERNEL && GENERIC_HARDIRQS
+	help
+	  Enable this to generate a spurious interrupt as soon as a shared
+	  interrupt handler is registered, and just before one is deregistered.
+	  Drivers ought to be able to handle interrupts coming in at those
+	  points; some don't and need to be caught.
+
 config LOG_BUF_SHIFT
 	int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
 	range 12 21