On Sat, Apr 05, 2008 at 01:48:02PM +0200, Geert Uytterhoeven wrote: > On Sat, 5 Apr 2008, Adrian Bunk wrote: > > Commit aa02ad67d9b308290fde390682cd039b29f7ab85 > > "ext4: Add ext4_find_next_bit()" causes the following regression: > > > > <-- snip --> > > > > ... > > CC [M] fs/ext4/mballoc.o > > /home/bunk/linux/kernel-2.6/git/linux-2.6/fs/ext4/mballoc.c: In function 'mb_find_next_bit': > > /home/bunk/linux/kernel-2.6/git/linux-2.6/fs/ext4/mballoc.c:696: error: implicit declaration of function 'generic_find_next_le_bit' > > make[3]: *** [fs/ext4/mballoc.o] Error 1 > > > > <-- snip --> > > Known issue. The ext4 developers added a #define (with a different name than in > the patch comment) in the commit below, but forgot to make sure > generic_find_next_le_bit() is actually available. > generic_find_next_le_bit is defined in lib/find_next_bit.c. But m68k doesn't want to use the GENERIC_FIND_NEXT_BIT. Can I request somebody knowledgeable about m68k to give a try in implementing generic_find_next_le_bit equivalent on m68k ? -aneesh -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
