From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: compat-drivers wishlist
Date: Thu, 28 Mar 2013 23:32:09 +0100 [thread overview]
Message-ID: <1364509929.10397.79.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6U=_C72wQLQbXdqN88tudZr7U9Quk_FVeYSgYwEgzeusQ@mail.gmail.com> (sfid-20130328_232511_312472_24B65844)
On Thu, 2013-03-28 at 15:24 -0700, Luis R. Rodriguez wrote:
> Another thing I should mention here about Kconfig.
>
> 'make localmodconfig' is great and IMHO something which we should
> strive for as well for end users. The issue comes in when you have to
> build something for remote systems. For this I wrote a script a while
> ago to let us extract only the necessary components from the kernel,
> scp to target, and extract back our .config [0]. This is hacky but
> something to keep in mind.
Yes, that's another interesting thing to do. I myself tend to think it's
less important as even building all of compat shouldn't take all that
much time. OTOH, it's clearly a lot more than what you usually want.
The tricky part here is that for those users that have most reason to
use compat, those who need it for new driver modules, it won't work
because they can't already be loaded on the system.
Anyway I don't see why we couldn't just copy the streamline config perl
script, with the Kconfig tree we build it would probably work just fine.
johannes
next prev parent reply other threads:[~2013-03-28 22:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 21:49 compat-drivers wishlist Johannes Berg
2013-03-28 22:15 ` Luis R. Rodriguez
2013-03-28 22:24 ` Luis R. Rodriguez
2013-03-28 22:32 ` Johannes Berg [this message]
2013-03-28 22:27 ` Johannes Berg
2013-03-28 22:54 ` Hauke Mehrtens
2013-03-28 23:01 ` Johannes Berg
2013-03-28 22:20 ` Johannes Berg
2013-03-28 22:40 ` Hauke Mehrtens
2013-03-28 22:59 ` Johannes Berg
2013-03-28 23:23 ` Luis R. Rodriguez
2013-03-28 23:40 ` Johannes Berg
2013-03-29 0:08 ` Luis R. Rodriguez
2013-03-30 18:30 ` Johannes Berg
2013-03-30 21:35 ` Luis R. Rodriguez
2013-03-30 21:48 ` Johannes Berg
2013-03-30 22:06 ` Luis R. Rodriguez
2013-03-30 0:29 ` Johannes Berg
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=1364509929.10397.79.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=mcgrof@do-not-panic.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.