[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK8P3a0wky-Km=PQO9=jN2kC0Zyy75LfD-1Kn5YHiEEV8ymZHQ@mail.gmail.com>
Date: Wed, 22 May 2019 23:20:00 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Donnellan <ajd@...ux.ibm.com>,
Eric Piel <eric.piel@...mplin-utc.net>,
Frank Haverkamp <haver@...ux.ibm.com>,
Frederic Barrat <fbarrat@...ux.ibm.com>,
Michał Mirosław <mirq-linux@...e.qmqm.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [PATCH] misc: remove redundant 'default n' from Kconfig-s
On Mon, May 20, 2019 at 4:10 PM Bartlomiej Zolnierkiewicz
<b.zolnierkie@...sung.com> 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 <b.zolnierkie@...sung.com>
Acked-by: Arnd Bergmann <arnd@...db.de>
Powered by blists - more mailing lists