summaryrefslogtreecommitdiff
path: root/arch/m68k/configs/mvme16x_defconfig
diff options
context:
space:
mode:
authorBartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>2018-10-16 15:33:58 +0200
committerGeert Uytterhoeven <geert@linux-m68k.org>2018-12-03 13:05:42 +0100
commitaf5d7a36d196654220b6f9172915a8c2d0bef33f (patch)
tree48b2b3405da6145c182dff48ea6e2501f2114062 /arch/m68k/configs/mvme16x_defconfig
parentb6cf523c16e148e1ece5fc4ff4657d79323a4635 (diff)
m68k: Remove redundant 'default n' from Kconfig
'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: Geert Uytterhoeven <geert@linux-m68k.org>
Diffstat (limited to 'arch/m68k/configs/mvme16x_defconfig')
0 files changed, 0 insertions, 0 deletions