719736e1cc
'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: Michael Ellerman <mpe@ellerman.id.au>
15 lines
227 B
Plaintext
15 lines
227 B
Plaintext
# SPDX-License-Identifier: GPL-2.0
|
|
config PPC_XIVE
|
|
bool
|
|
select PPC_SMP_MUXED_IPI
|
|
select HARDIRQS_SW_RESEND
|
|
|
|
config PPC_XIVE_NATIVE
|
|
bool
|
|
select PPC_XIVE
|
|
depends on PPC_POWERNV
|
|
|
|
config PPC_XIVE_SPAPR
|
|
bool
|
|
select PPC_XIVE
|