From: Ross Burton <ross@burtonini.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Bruce Ashfield <bruce.ashfield@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/2] kernel-module-split: modules should recommend the kernel image
Date: Thu, 10 Feb 2022 11:45:41 +0000 [thread overview]
Message-ID: <CAAnfSTujoz8v_+Cddjut2mO5d2FNDYBZtnXR87j8Ych_wYoEnA@mail.gmail.com> (raw)
In-Reply-To: <c54b8a5fbe59b21a862d5b6519e4f8872458f694.camel@linuxfoundation.org>
On Thu, 10 Feb 2022 at 10:54, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> > Obviously this won't work in the situations where you want a normal
> > image with a kernel but also a initramfs with a kernel module in it,
> > as that behaviour isn't machine specific but image specific.
> >
> > If this was a recommends then it could be removed via PACKAGE_EXCLUDE,
> > but we'd need to be sure that nothing from the kernel ended up getting
> > pulled in via a single module.
>
> I think making this a RRECOMMENDS and doing that may enable more workflows and
> make things easier all around. Can you check and see if it does pull other
> unwanted stuff in? I'm hoping it doesn't.
Tested. Our initramfs pulls in a kernel module, and
PACKAGE_EXCLUDE=kernel-image-* stops the image itself being pulled in.
It does pull in the kernel-5.15-yocto-standard package, but that just
contains a few module config files.
Patch incoming!
Ross
prev parent reply other threads:[~2022-02-10 11:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 17:30 [PATCH 1/2] package: add extra_recommends to do_split_package() Ross Burton
2022-02-09 17:30 ` [PATCH 2/2] kernel-module-split: modules should recommend the kernel image Ross Burton
2022-02-09 17:36 ` Bruce Ashfield
2022-02-09 17:56 ` [OE-core] " Khem Raj
2022-02-09 18:03 ` Bruce Ashfield
2022-02-09 19:13 ` Richard Purdie
2022-02-09 20:10 ` Bruce Ashfield
2022-02-10 10:52 ` Ross Burton
2022-02-10 10:54 ` Richard Purdie
2022-02-10 11:45 ` Ross Burton [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=CAAnfSTujoz8v_+Cddjut2mO5d2FNDYBZtnXR87j8Ych_wYoEnA@mail.gmail.com \
--to=ross@burtonini.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 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.