So, on 5.0 kernels the build does not fail because modpost is more relaxed and will throw warnings on undefined symbols, whereas with 5.2 modpost throws an error.
Interesting fact is that modprobing the razercore on a 5.0 s390 kernel will fail with: [ 2553.134689] razercore: Unknown symbol hid_unregister_driver (err -2) [ 2553.134703] razercore: Unknown symbol hid_hw_start (err -2) [ 2553.134725] razercore: Unknown symbol __hid_register_driver (err -2) [ 2553.134748] razercore: Unknown symbol hid_hw_stop (err -2) [ 2553.134782] razercore: Unknown symbol usb_control_msg (err -2) [ 2553.134804] razercore: Unknown symbol usb_disable_autosuspend (err -2) [ 2553.134820] razercore: Unknown symbol hid_open_report (err -2) And on 5.2 it just won't build because of modpost being more proactive at checking this. I think the modpost should be relaxed so at least it will build on 5.2. It may not load with our kernel, but I guess if somebody wants it they need to have their own kernel with the hid support for s390x (which probably does not exist). Alternatively we could disable the build for s390x. I'd prefer to relax odpost as we leave room for a user to at least use their own kernel that may support this driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830055 Title: openrazer 2.5.0+dfsg-1 ADT test failure with linux 5.2.0-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openrazer/+bug/1830055/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
