From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: koen@dominion.thruhere.net
Subject: Re: [PATCH] kernel.bbclass: blacklist 'kernel-misc' from kernel-modules
Date: Wed, 23 Mar 2011 23:05:05 +0000 [thread overview]
Message-ID: <1300921505.3018.46.camel@rex> (raw)
In-Reply-To: <AANLkTimczMoBaP67GMz+pc11A0arZejWj4=yQrki52W-@mail.gmail.com>
On Wed, 2011-03-23 at 13:18 -0700, Khem Raj wrote:
> On Wed, Mar 23, 2011 at 12:55 PM, <koen@dominion.thruhere.net> wrote:
> > From: Koen Kooi <koen@dominion.thruhere.net>
> >
> > When 'kernel-misc' is empty do_rootfs will fail when including 'kernel-modules'
> >
> > The proper fix would be to have a whitelist for the 'kernel-modules' meta-pkg
> >
> > Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
>
> Worked nicely.
>
> Tested-by: Khem Raj <raj.khem@gmail.com>
>
> > ---
> > meta/classes/kernel.bbclass | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> > index 3eb6659..9f014d4 100644
> > --- a/meta/classes/kernel.bbclass
> > +++ b/meta/classes/kernel.bbclass
> > @@ -429,7 +429,7 @@ python populate_packages_prepend () {
> > metapkg = "kernel-modules"
> > bb.data.setVar('ALLOW_EMPTY_' + metapkg, "1", d)
> > bb.data.setVar('FILES_' + metapkg, "", d)
> > - blacklist = [ 'kernel-dev', 'kernel-image', 'kernel-base', 'kernel-vmlinux', 'perf' ]
> > + blacklist = [ 'kernel-dev', 'kernel-image', 'kernel-base', 'kernel-vmlinux', 'perf', 'kernel-misc' ]
> > for l in module_deps.values():
> > for i in l:
> > pkg = module_pattern % legitimize_package_name(re.match(module_regex, os.path.basename(i)).group(1))
Merged to master, thanks!
Richard
prev parent reply other threads:[~2011-03-23 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 19:55 [PATCH] kernel.bbclass: blacklist 'kernel-misc' from kernel-modules koen
2011-03-23 20:18 ` Khem Raj
2011-03-23 23:05 ` Richard Purdie [this message]
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=1300921505.3018.46.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.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