[lkml]   [2018]   [Dec]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] m68k: remove redundant 'default n' from Kconfig
On Tue, Oct 16, 2018 at 3:34 PM Bartlomiej Zolnierkiewicz
<> wrote:
> '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
> bool
> config FOO
> bool
> 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
> redundant.
> ...
> Signed-off-by: Bartlomiej Zolnierkiewicz <>

Reviewed-by: Geert Uytterhoeven <>
I.e., applied and queued for v4.21.



Geert Uytterhoeven -- There's lots of Linux beyond ia32 --

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

 \ /
  Last update: 2018-12-03 13:30    [W:0.041 / U:1.676 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site