Bartlomiej Zolnierkiewicz dc3e0aa5c5 misc: remove redundant 'default n' from Kconfig-s ... '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 f467c5640c ("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@samsung.com> Acked-by: Frederic Barrat <fbarrat@linux.ibm.com> Acked-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Michael Ellerman <mpe@ellerman.id.au> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2019-05-24 18:00:41 +02:00
..
c2port-duramar2150.c
core.c	kmemcheck: remove annotations	2017-11-15 18:21:04 -08:00
Kconfig	misc: remove redundant 'default n' from Kconfig-s	2019-05-24 18:00:41 +02:00
Makefile