None of the autobuilders are finding this problem, and they build a wide range of configurations. Maybe it's something specific to how you're building the kernel - can you give step by step instructions how to reproduce this please? On Sun, Nov 20, 2016 at 03:47:34AM +0100, Tobias Jakobi wrote: > Hello, > > this is a resend of my initial mail, see below, to Al Viro (which sadly > was ignored). > > It's rc5 now, and this issue still remains. Putting some more lists on > the Cc now. > > Reverting the commit still works for me. > > > With best wishes, > Tobias > > ---------------- > > > Hello Al, > > compiled a kernel on armv7 with torvalds/master today and getting some > errors during the modpost phase. > > > ERROR: "_set_bit" [sound/usb/snd-usbmidi-lib.ko] undefined! > > ERROR: "_test_and_set_bit" [sound/usb/snd-usbmidi-lib.ko] undefined! > > ERROR: "_clear_bit" [sound/usb/snd-usbmidi-lib.ko] undefined! > > ERROR: "_test_and_clear_bit" [sound/usb/snd-usb-audio.ko] undefined! > > ERROR: "_set_bit" [sound/usb/snd-usb-audio.ko] undefined! > > ERROR: "_test_and_set_bit" [sound/usb/snd-usb-audio.ko] undefined! > > ERROR: "_clear_bit" [sound/usb/snd-usb-audio.ko] undefined! > > ERROR: "_test_and_clear_bit" [sound/core/seq/snd-seq.ko] undefined! > <snip> > > It seems like the commit 'arm: move exports to definitions' introduces > this issue. > > I quickly went over the commit and I noticed that while it removes the > EXPORT_SYMBOL()s for the bitops from armksyms.c, it doesn't move them > anywhere. > > Maybe you can take a look at this? > > With best wishes, > Tobias > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |