Kconfig: eliminate "def_bool n" constructs
Using "def_bool n" is pointless, simply using bool here appears more appropriate. Further, retaining such options that don't have a prompt and aren't selected by anything seems also at least questionable. Signed-off-by: Jan Beulich <jbeulich@novell.com> Cc: Ingo Molnar <mingo@elte.hu> Cc: Tony Luck <tony.luck@intel.com> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> Cc: Sam Ravnborg <sam@ravnborg.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
committed by
Linus Torvalds
parent
a25d644fc0
commit
9ba16087d9
@ -101,7 +101,7 @@ config HAVE_MEMORY_PRESENT
|
||||
# with gcc 3.4 and later.
|
||||
#
|
||||
config SPARSEMEM_STATIC
|
||||
def_bool n
|
||||
bool
|
||||
|
||||
#
|
||||
# Architecture platforms which require a two level mem_section in SPARSEMEM
|
||||
@ -113,7 +113,7 @@ config SPARSEMEM_EXTREME
|
||||
depends on SPARSEMEM && !SPARSEMEM_STATIC
|
||||
|
||||
config SPARSEMEM_VMEMMAP_ENABLE
|
||||
def_bool n
|
||||
bool
|
||||
|
||||
config SPARSEMEM_VMEMMAP
|
||||
bool "Sparse Memory virtual memmap"
|
||||
|
Reference in New Issue
Block a user