From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Phil Blundell <philb@gnu.org>,
openembedded-core@lists.openembedded.org,
Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [PATCH] kernel.bbclass: Allow modules.tar.gz generation to be inhibited
Date: Mon, 24 Sep 2012 10:56:27 +0100 [thread overview]
Message-ID: <1348480587.4486.5.camel@ted> (raw)
In-Reply-To: <CAJTo0Lbi+KEu1=857m0v5xX0geWHA4pDuQqHgALyMt2rPLD8XQ@mail.gmail.com>
On Mon, 2012-09-24 at 09:36 +0100, Burton, Ross wrote:
> On 24 September 2012 00:22, Philip Balister <philip@balister.org> wrote:
> >>> Allow it to be suppressed by setting KERNEL_DEPLOY_MODULE_TARBALL=0.
> >>
> >> I'm wondering, does anyone still find this file useful?
> >
> > I've used it to put modules in rootfs when there is a new kernel version and
> > I do not have easy access to packages feeds. This speeds testing.
>
> Sounds like a less than common use-case. How about setting it to 0 by default?
I know I used to use this file a lot when working on Zaurus kernels.
These days I don't get to play with hardware as much as I'd like so I've
not used it in a while.
It is extremely useful when you need it. I've always argued there are
much more problematic time sinks in the build than this tarball
creation...
Cheers,
Richard
next prev parent reply other threads:[~2012-09-24 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 21:45 [PATCH] kernel.bbclass: Allow modules.tar.gz generation to be inhibited Phil Blundell
2012-09-23 22:20 ` Paul Eggleton
2012-09-23 23:22 ` Philip Balister
2012-09-24 8:36 ` Burton, Ross
2012-09-24 9:56 ` Richard Purdie [this message]
2012-09-24 12:05 ` Philip Balister
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=1348480587.4486.5.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=philb@gnu.org \
--cc=ross.burton@intel.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.