From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
Petr Vorel <petr.vorel@gmail.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: Possible to build-in backports modules into kernel
Date: Fri, 17 Apr 2015 20:26:06 +0200 [thread overview]
Message-ID: <1429295166.1885.6.camel@sipsolutions.net> (raw)
In-Reply-To: <55314F5C.3000907@lwfinger.net> (sfid-20150417_202224_271161_EC945DE9)
On Fri, 2015-04-17 at 13:22 -0500, Larry Finger wrote:
> On 04/17/2015 01:03 PM, Luis R. Rodriguez wrote:
> > On Fri, Apr 17, 2015 at 10:28 AM, Johannes Berg
> > <johannes@sipsolutions.net> wrote:
> >> Technically this is not true any more - the backports gentree.py script
> >> now supports kernel integration where it copies the backport into
> >> another kernel tree :)
> >
> > Indeed:
> >
> > https://backports.wiki.kernel.org/index.php/Documentation/integration
>
> Just to clarify, the entire kernel will need to be built from some tree. In my
> reading of the original post, I got the impression that Petr wanted to use a
> pre-built kernel.
Yes, indeed, that's not possible - and doesn't really make sense anyway,
since if you have access to the kernel image and sources to build
against, you might as well rebuild the whole kernel.
johannes
next prev parent reply other threads:[~2015-04-17 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 13:30 Possible to build-in backports modules into kernel Petr Vorel
2015-04-17 16:14 ` Larry Finger
2015-04-17 17:28 ` Johannes Berg
2015-04-17 18:03 ` Luis R. Rodriguez
2015-04-17 18:22 ` Larry Finger
2015-04-17 18:26 ` Johannes Berg [this message]
2015-04-17 21:42 ` Petr Vorel
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=1429295166.1885.6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=backports@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=petr.vorel@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.