From: "John W. Linville" <linville@tuxdriver.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: "Luis R. Rodriguez" <mcgrof@frijolero.org>,
linux-kernel@vger.kernel.org, Dave Jones <davej@redhat.com>,
Greg KH <greg@kroah.com>,
Debian kernel maintainers <debian-kernel@lists.debian.org>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-wireless@vger.kernel.org
Subject: Re: [RFC] modpost: add option to allow external modules to avoid taint
Date: Wed, 14 Dec 2011 12:39:22 -0500 [thread overview]
Message-ID: <20111214173922.GA2607@tuxdriver.com> (raw)
In-Reply-To: <1323881520.2825.196.camel@deadeye>
On Wed, Dec 14, 2011 at 04:52:00PM +0000, Ben Hutchings wrote:
> 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@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.
> [...]
>
> If you're integrating it then why can't you *really* build it in-tree?
Well, of course, I could. But it would be a _huge_ waste of my time
doing so. The compat-wireless package is already sitting there,
complete with all the necessary backporting infrastructure. It's all
fat and juicy, waiting to be used. Wasting time replicating that
just doesn't make any sense to my mind.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-12-14 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1319461948.31243.31.camel@deadeye>
2011-12-12 21:40 ` [PATCH] module,bug: Add TAINT_OOT_MODULE flag for modules not built in-tree Luis R. Rodriguez
2011-12-12 21:58 ` Ben Hutchings
2011-12-12 22:47 ` Luis R. Rodriguez
2011-12-12 22:49 ` Luis R. Rodriguez
2011-12-13 5:02 ` Ben Hutchings
2011-12-14 16:20 ` [RFC] modpost: add option to allow external modules to avoid taint John W. Linville
2011-12-14 16:52 ` Ben Hutchings
2011-12-14 17:39 ` John W. Linville [this message]
[not found] ` <87mxatp3ty.fsf@rustcorp.com.au>
2011-12-16 4:39 ` Ben Hutchings
2011-12-19 5:45 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111214173922.GA2607@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ben@decadent.org.uk \
--cc=davej@redhat.com \
--cc=debian-kernel@lists.debian.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).