From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Phil Blundell <philb@gnu.org>
Subject: Re: [PATCH] kernel.bbclass: Allow modules.tar.gz generation to be inhibited
Date: Sun, 23 Sep 2012 23:20:44 +0100 [thread overview]
Message-ID: <1540243.ihgQ8YivHP@helios> (raw)
In-Reply-To: <1348436710.4444.247.camel@x121e.pbcl.net>
On Sunday 23 September 2012 22:45:10 Phil Blundell wrote:
> The modules.tar.gz archive is sometimes of no value and it can take
> a noticeable time to build if many modules were enabled in the kernel
> configuration. The extraneous file also contributes to deploy/ clutter
> and is a waste of disk space.
>
> Allow it to be suppressed by setting KERNEL_DEPLOY_MODULE_TARBALL=0.
I'm wondering, does anyone still find this file useful?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-09-23 22:33 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 [this message]
2012-09-23 23:22 ` Philip Balister
2012-09-24 8:36 ` Burton, Ross
2012-09-24 9:56 ` Richard Purdie
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=1540243.ihgQ8YivHP@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.org \
/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