[lkml]   [2018]   [Oct]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
Subject[PATCH] m68k: remove redundant 'default n' from Kconfig
'default n' is the default value for any bool or tristate Kconfig
setting so there is no need to write it explicitly.

Also since commit f467c5640c29 ("kconfig: only write '# CONFIG_FOO
is not set' for visible symbols") the Kconfig behavior is the same
regardless of 'default n' being present or not:

One side effect of (and the main motivation for) this change is making
the following two definitions behave exactly the same:

config FOO

config FOO
default n

With this change, neither of these will generate a
'# CONFIG_FOO is not set' line (assuming FOO isn't selected/implied).
That might make it clearer to people that a bare 'default n' is

Signed-off-by: Bartlomiej Zolnierkiewicz <>
arch/m68k/Kconfig.machine | 2 --
1 file changed, 2 deletions(-)

Index: b/arch/m68k/Kconfig.machine
--- a/arch/m68k/Kconfig.machine 2018-09-03 18:11:11.397792454 +0200
+++ b/arch/m68k/Kconfig.machine 2018-10-16 15:32:04.359635259 +0200
@@ -317,7 +317,6 @@ config UBOOT
If you say Y here kernel will try to collect command
line parameters from the initial u-boot stack.
- default n

config 4KSTACKS
bool "Use 4Kb for kernel stacks instead of 8Kb"
@@ -395,7 +394,6 @@ comment "ROM configuration"

config ROM
bool "Specify ROM linker regions"
- default n
Define a ROM region for the linker script. This creates a kernel
that can be stored in flash, with possibly the text, and data
 \ /
  Last update: 2018-10-16 15:34    [W:0.032 / U:4.220 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site