Re: [PATCH] misc: remove redundant 'default n' from Kconfig-s

2019-05-22 Thread Arnd Bergmann
On Mon, May 20, 2019 at 4:10 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") th

Re: [PATCH] misc: remove redundant 'default n' from Kconfig-s

2019-05-21 Thread Frederic Barrat
Le 20/05/2019 à 16:10, Bartlomiej Zolnierkiewicz a écrit : '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 beh

Re: [PATCH] misc: remove redundant 'default n' from Kconfig-s

2019-05-21 Thread Michael Ellerman
Bartlomiej Zolnierkiewicz writes: > '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 >

Re: [PATCH] misc: remove redundant 'default n' from Kconfig-s

2019-05-20 Thread Michał Mirosław
On Mon, May 20, 2019 at 04:10:46PM +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 symb

[PATCH] misc: remove redundant 'default n' from Kconfig-s

2019-05-20 Thread Bartlomiej Zolnierkiewicz
'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