From: Patrick Ohly <patrick.ohly@intel.com>
To: wei.tee.ng@intel.com, openembedded-core@lists.openembedded.org
Cc: saul.wold@intel.com
Subject: Re: [PATCH 2/3] initramfs-framework: include install-efi module in recipe for installation
Date: Mon, 31 Jul 2017 21:39:44 +0200 [thread overview]
Message-ID: <1501529984.18875.33.camel@intel.com> (raw)
In-Reply-To: <f6e284a595aaa7b2444dc521407f8dc5ed6e8961.1500848692.git.wei.tee.ng@intel.com>
On Sun, 2017-07-23 at 16:51 -0700, wei.tee.ng@intel.com wrote:
> +
> +SUMMARY_initramfs-module-install-efi = "initramfs support for installation option"
> +RDEPENDS_initramfs-module-install-efi = "${PN}-base parted e2fsprogs-mke2fs dosfstools util-linux-blkid"
> +FILES_initramfs-module-install-efi = "/init.d/install-efi.sh"
By making the install-efi module a part of initramfs-module that is
enabled unconditionally, parted now needs to be built for the target
even when only the rest of initramfs-module is used.
Can the module please be split out into its own recipe?
Alternatively one could add a PACKAGECONFIG for it, but that's less
flexible.
--
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-07-31 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 23:51 [poky][master][PATCH 0/3] core-image-minimal-initramfs: use initramfs-framework for initialization by default wei.tee.ng
2017-07-23 23:51 ` [PATCH 1/3] initramfs-framework: module to support boot live image wei.tee.ng
2017-07-23 23:51 ` [PATCH 2/3] initramfs-framework: include install-efi module in recipe for installation wei.tee.ng
2017-07-31 19:39 ` Patrick Ohly [this message]
2017-07-23 23:51 ` [PATCH 3/3] core-image-minimal-initramfs: use initramfs-framework by default wei.tee.ng
2017-07-30 7:47 ` Richard Purdie
2017-08-04 7:17 ` Ng, Wei Tee
2017-08-04 20:54 ` Cal Sullivan
2017-08-04 21:20 ` [PATCH] initramfs-framework/setup-live: also boot live image if root=/dev/ram0 California Sullivan
2017-08-04 21:31 ` ✗ patchtest: failure for core-image-minimal-initramfs: use initramfs-framework for initialization by default (rev2) Patchwork
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=1501529984.18875.33.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.com \
--cc=wei.tee.ng@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox