On Wed, 14 Dec 2011 11:20:03 -0500, "John W. Linville" <linvi...@tuxdriver.com> wrote: > In some cases, it might be desirable to package a module from an > external source tree alongside the base kernel. In those cases, it > might also be desirable to not have those modules tainting the kernel. > > This patch provides a mechanism for an external module build to declare > itself as an "integrated build". Such a module is then treated the same > as an intree module. > > Signed-off-by: John W. Linville <linvi...@tuxdriver.com> > --- > Any thoughts on this? I'm thinking of adding this to Fedora kernels, > where I have been working to integrate the compat-wireless package as > part of the base kernel RPM.
I don't think the feature is useful it it's too easy to disable. Experience has shown this with license tags. We really want to indicate "out-of-support" which is only a 1:1 mapping to out-of-tree for upstream kernels. How does Debian handle this? Perhaps it makes more sense to use the proposed module signing stuff in a simplified mode to mark built-with-kernel modules (eg. just put the sha of known modules inside the kernel). I think we should revert this change, meanwhile, and figure out what to do. Cheers, Rusty. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87mxatp3ty....@rustcorp.com.au
