CONFIG_DEBUG_KERNEL should not impact code generation. Use the newly defined CONFIG_DEBUG_MISC instead to keep the current code.
Signed-off-by: Sinan Kaya <ok...@kernel.org> Reviewed-by: Josh Triplett <j...@joshtriplett.org> --- arch/mips/kernel/setup.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c index 8d1dc6c71173..9fc8fadb8418 100644 --- a/arch/mips/kernel/setup.c +++ b/arch/mips/kernel/setup.c @@ -563,7 +563,7 @@ static void __init bootmem_init(void) offset = __pa_symbol(_text) - __pa_symbol(VMLINUX_LOAD_ADDRESS); memblock_free(__pa_symbol(VMLINUX_LOAD_ADDRESS), offset); -#if defined(CONFIG_DEBUG_KERNEL) && defined(CONFIG_DEBUG_INFO) +#if defined(CONFIG_DEBUG_MISC) && defined(CONFIG_DEBUG_INFO) /* * This information is necessary when debugging the kernel * But is a security vulnerability otherwise! -- 2.21.0