Re: [PATCH] x86: remove redundant 'default n' from Kconfig-s
From: Borislav Petkov
Date: Wed Oct 17 2018 - 04:34:14 EST
On Tue, Oct 16, 2018 at 03:42:16PM +0200, 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
> 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 <b.zolnierkie@xxxxxxxxxxx>
> arch/x86/Kconfig | 7 -------
> arch/x86/Kconfig.debug | 1 -
> arch/x86/xen/Kconfig | 1 -
> 3 files changed, 9 deletions(-)
looks good, no difference of allmodconfigs before and after.
But that close before the merge window and it not being urgent, I'll
queue it after the merge window.
Good mailing practices for 400: avoid top-posting and trim the reply.