From: Patrick Ohly <patrick.ohly@intel.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v4] initramfs-framework: Change recipe to be allarch
Date: Wed, 30 Aug 2017 15:24:58 +0200 [thread overview]
Message-ID: <1504099498.12799.41.camel@intel.com> (raw)
In-Reply-To: <CAP9ODKqSH7PNk1fATkb6CGiwkKAnkuR5d2esZtVbzp77b2n3Mg@mail.gmail.com>
On Wed, 2017-08-30 at 09:46 -0300, Otavio Salvador wrote:
> On Wed, Aug 30, 2017 at 6:39 AM, Patrick Ohly <patrick.ohly@intel.co
> wrote:
> > Let's not dig us deeper into this hole and instead split out the
> > live
> > boot module into its own, arch-specific recipe.
> >
> > Then initramfs-framework can become allarch without having to make
> > layer.conf more complicated.
>
> I think this can be in two steps. Splitting it out makes sense as it
> avoids the build of useless packages if someone is not using the live
> modules but it can be another patch.
I'm not sure in which order you want to get it done: first split out,
then update (i.e. remove the layer.conf change) your patch and merge
that, or apply the v4 revision of your patch and later clean up
(including removal of the layer.conf change)?
Personally I'm in favor of first splitting out the modules.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-08-30 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 20:43 [PATCH v4] initramfs-framework: Change recipe to be allarch Otavio Salvador
2017-08-30 9:39 ` Patrick Ohly
2017-08-30 12:46 ` Otavio Salvador
2017-08-30 13:24 ` Patrick Ohly [this message]
2017-08-30 13:29 ` Otavio Salvador
2017-09-01 6:45 ` Patrick Ohly
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=1504099498.12799.41.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=otavio@ossystems.com.br \
/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