[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1323881520.2825.196.camel@deadeye>
Date: Wed, 14 Dec 2011 16:52:00 +0000
From: Ben Hutchings <ben@...adent.org.uk>
To: "John W. Linville" <linville@...driver.com>
Cc: "Luis R. Rodriguez" <mcgrof@...jolero.org>,
linux-kernel@...r.kernel.org, Dave Jones <davej@...hat.com>,
Greg KH <greg@...ah.com>,
Debian kernel maintainers <debian-kernel@...ts.debian.org>,
Rusty Russell <rusty@...tcorp.com.au>,
linux-wireless@...r.kernel.org
Subject: Re: [RFC] modpost: add option to allow external modules to avoid
taint
On Wed, 2011-12-14 at 11:20 -0500, John W. Linville 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 <linville@...driver.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.
[...]
If you're integrating it then why can't you *really* build it in-tree?
Ben.
--
Ben Hutchings
Computers are not intelligent. They only think they are.
Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)
Powered by blists - more mailing lists