diff options
| author | Alexander van Heukelum <heukelum@mailshack.com> | 2008-04-25 13:12:53 +0200 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2008-04-26 19:21:17 +0200 |
| commit | 19870def587554c4055df3e74a21508e3647fb7e (patch) | |
| tree | d1c483a58e0ec684b8e3678a906dc115ffee5006 /fs | |
| parent | f19dcf4a61ea4a3d155acb239348d09cb264f6a0 (diff) | |
| download | linux-19870def587554c4055df3e74a21508e3647fb7e.tar.bz2 | |
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 'fs')
0 files changed, 0 insertions, 0 deletions