aboutsummaryrefslogtreecommitdiff
path: root/arch/um/Kconfig.x86_64
diff options
context:
space:
mode:
authorAlexander van Heukelum <heukelum@mailshack.com>2008-04-25 13:12:53 +0200
committerIngo Molnar <mingo@elte.hu>2008-04-26 19:21:17 +0200
commit19870def587554c4055df3e74a21508e3647fb7e (patch)
treed1c483a58e0ec684b8e3678a906dc115ffee5006 /arch/um/Kconfig.x86_64
parentf19dcf4a61ea4a3d155acb239348d09cb264f6a0 (diff)
downloadlinux-2.6.34-ux500-19870def587554c4055df3e74a21508e3647fb7e.tar.gz
x86, bitops: select the generic bitmap search functions
Introduce GENERIC_FIND_FIRST_BIT and GENERIC_FIND_NEXT_BIT in lib/Kconfig, defaulting to off. An arch that wants to use the generic implementation now only has to use a select statement to include them. I added an always-y option (X86_CPU) to arch/x86/Kconfig.cpu and used that to select the generic search functions. This way ARCH=um SUBARCH=i386 automatically picks up the change too, and arch/um/Kconfig.i386 can therefore be simplified a bit. ARCH=um SUBARCH=x86_64 does things differently, but still compiles fine. It seems that a "def_bool y" always wins over a "def_bool n"? Signed-off-by: Alexander van Heukelum <heukelum@fastmail.fm> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch/um/Kconfig.x86_64')
-rw-r--r--arch/um/Kconfig.x86_648
1 files changed, 0 insertions, 8 deletions
diff --git a/arch/um/Kconfig.x86_64 b/arch/um/Kconfig.x86_64
index cc42e59585d..5696e7b374b 100644
--- a/arch/um/Kconfig.x86_64
+++ b/arch/um/Kconfig.x86_64
@@ -34,14 +34,6 @@ config SMP_BROKEN
bool
default y
-config GENERIC_FIND_FIRST_BIT
- bool
- default y
-
-config GENERIC_FIND_NEXT_BIT
- bool
- default y
-
config GENERIC_HWEIGHT
bool
default y