From: Adrian Bunk I know several people using MAGIC_SYSRQ not for kernel debugging but for trying to do a halfway normal shutdown in case of problems. Since there's no technical reason why MAGIC_SYSRQ would have to depend on DEBUG_KERNEL, I'm therefore suggesting to drop this dependency. Signed-off-by: Adrian Bunk Signed-off-by: Andrew Morton --- lib/Kconfig.debug | 15 +++++++-------- 1 files changed, 7 insertions(+), 8 deletions(-) diff -puN lib/Kconfig.debug~let-magic_sysrq-no-longer-depend-on-debug_kernel lib/Kconfig.debug --- devel/lib/Kconfig.debug~let-magic_sysrq-no-longer-depend-on-debug_kernel 2005-12-13 14:04:29.000000000 -0800 +++ devel-akpm/lib/Kconfig.debug 2005-12-13 14:04:29.000000000 -0800 @@ -8,16 +8,9 @@ config PRINTK_TIME operations. This is useful for identifying long delays in kernel startup. - -config DEBUG_KERNEL - bool "Kernel debugging" - help - Say Y here if you are developing drivers or trying to debug and - identify kernel problems. - config MAGIC_SYSRQ bool "Magic SysRq key" - depends on DEBUG_KERNEL && !UML + depends on !UML help If you say Y here, you will have some control over the system even if the system crashes for example during kernel debugging (e.g., you @@ -29,6 +22,12 @@ config MAGIC_SYSRQ keys are documented in . Don't say Y unless you really know what this hack does. +config DEBUG_KERNEL + bool "Kernel debugging" + help + Say Y here if you are developing drivers or trying to debug and + identify kernel problems. + config LOG_BUF_SHIFT int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL range 12 21 _