> Date: Wed, 2 Aug 2017 07:56:50 -0700 > From: Brian Buhrow <buh...@nfbcal.org> > > Hello. My feeling is that the cost of requiring a modload to use > compat_linux and compat_linux32 is fine. My concern is that by taking it > out of the GENERIC kernel configuration, we lose the regular testing, such > as it is, with the daily builds. Sure, the module gets built, but it could > be a while before it gets loaded and run by the test harness. Today, with > these modules in GENERIC, the modules get loaded as a matter of course. > Is there a way to rig our test harness so that you can take the modules out > of the GENERIC kernel configuration and still do more than compile-time > test them?
We do not currently automatically test the compat modules as far as I know. Volunteers are welcome to write automated tests of compat! (The code will also continue to be compile-tested as non-module via the ALL kernels.)