From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Petr Vorel <petr.vorel@gmail.com>, backports@vger.kernel.org
Subject: Re: Possible to build-in backports modules into kernel
Date: Fri, 17 Apr 2015 19:28:40 +0200 [thread overview]
Message-ID: <1429291720.1885.5.camel@sipsolutions.net> (raw)
In-Reply-To: <5531314D.1000706@lwfinger.net> (sfid-20150417_181411_559997_6D84A8C0)
On Fri, 2015-04-17 at 11:14 -0500, Larry Finger wrote:
> The short answer is no for the backports code. If you want them built-in, grab
> the mainline 4.0 or 3.19.4 source, configure, and build a complete new kernel.
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 :)
johannes
next prev parent reply other threads:[~2015-04-17 17:28 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 [this message]
2015-04-17 18:03 ` Luis R. Rodriguez
2015-04-17 18:22 ` Larry Finger
2015-04-17 18:26 ` Johannes Berg
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=1429291720.1885.5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=backports@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox