diff options
author | Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> | 2018-10-09 16:32:54 +0200 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2018-10-10 14:11:07 -0600 |
commit | 1306ad4e60de57022a90b1904870763a39adcb42 (patch) | |
tree | 35efc619580766cc4570683433514f92032b33dc /mm | |
parent | 766c8ceb16fce904d6b8985ca2c0a547e053d1d5 (diff) | |
download | talos-obmc-linux-1306ad4e60de57022a90b1904870763a39adcb42.tar.gz talos-obmc-linux-1306ad4e60de57022a90b1904870763a39adcb42.zip |
block: 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 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@samsung.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions