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 <[email protected]>
Signed-off-by: Ingo Molnar <[email protected]>
This commit is contained in:
Alexander van Heukelum 2008-04-25 13:12:53 +02:00 • committed by Ingo Molnar
commit 19870def58
5 changed files with 11 additions and 22 deletions

View file

@ -7,6 +7,12 @@ menu "Library routines"
config BITREVERSE
tristate
config GENERIC_FIND_FIRST_BIT
def_bool n
config GENERIC_FIND_NEXT_BIT
def_bool n
config CRC_CCITT
tristate "CRC-CCITT functions"
help