bitops: introduce CONFIG_GENERIC_FIND_BIT_LE
This introduces CONFIG_GENERIC_FIND_BIT_LE to tell whether to use generic implementation of find_*_bit_le() in lib/find_next_bit.c or not. For now we select CONFIG_GENERIC_FIND_BIT_LE for all architectures which enable CONFIG_GENERIC_FIND_NEXT_BIT. But m68knommu wants to define own faster find_next_zero_bit_le() and continues using generic find_next_{,zero_}bit(). (CONFIG_GENERIC_FIND_NEXT_BIT and !CONFIG_GENERIC_FIND_BIT_LE) Signed-off-by:Akinobu Mita <akinobu.mita@gmail.com> Cc: Greg Ungerer <gerg@uclinux.org> Cc: Arnd Bergmann <arnd@arndb.de> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
Showing
- arch/frv/Kconfig 4 additions, 0 deletionsarch/frv/Kconfig
- arch/h8300/Kconfig 4 additions, 0 deletionsarch/h8300/Kconfig
- arch/m32r/Kconfig 4 additions, 0 deletionsarch/m32r/Kconfig
- arch/m68knommu/Kconfig 4 additions, 0 deletionsarch/m68knommu/Kconfig
- arch/microblaze/Kconfig 3 additions, 0 deletionsarch/microblaze/Kconfig
- arch/mips/Kconfig 4 additions, 0 deletionsarch/mips/Kconfig
- arch/parisc/Kconfig 4 additions, 0 deletionsarch/parisc/Kconfig
- arch/powerpc/Kconfig 4 additions, 0 deletionsarch/powerpc/Kconfig
- arch/sh/Kconfig 3 additions, 0 deletionsarch/sh/Kconfig
- arch/sparc/Kconfig 4 additions, 0 deletionsarch/sparc/Kconfig
- arch/xtensa/Kconfig 3 additions, 0 deletionsarch/xtensa/Kconfig
- lib/Kconfig 3 additions, 0 deletionslib/Kconfig
- lib/Makefile 1 addition, 0 deletionslib/Makefile
- lib/find_next_bit.c 3 additions, 0 deletionslib/find_next_bit.c
Loading
Please register or sign in to comment