Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ming Liu <ming.liu@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2] kernel.bbclass: add task dependency between bundle_initramfs and package
Date: Wed, 25 Jun 2014 15:13:08 +0800	[thread overview]
Message-ID: <53AA7684.7070105@windriver.com> (raw)
In-Reply-To: <1403661432-26466-1-git-send-email-ming.liu@windriver.com>

Please ignore this V2 too, I found a drawback that if the kernel-module* 
are added to the initramfs image, then it will lead us to a circular 
dependency risk, maybe we should not add this dependency at all.

//Ming Liu

On 06/25/2014 09:57 AM, Ming Liu wrote:
> To ensure the bundled image to be packaged into kernel-image, otherwise, If
> bundle_initramfs runs after do_package, the bundled kernel and initramfs
> will not be part of the kernel-image package. This can result in boot
> failures and other issues when the kernel-image is deployed.
>
> Signed-off-by: Ming Liu <ming.liu@windriver.com>
> ---
>   meta/classes/kernel.bbclass | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index 6ed1cb7..764a9ec 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -146,7 +146,7 @@ python do_devshell_prepend () {
>       os.environ["LDFLAGS"] = ''
>   }
>   
> -addtask bundle_initramfs after do_install before do_deploy
> +addtask bundle_initramfs after do_install before do_deploy do_package
>   
>   kernel_do_compile() {
>   	unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS MACHINE



      reply	other threads:[~2014-06-25  7:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25  1:57 [PATCH V2] kernel.bbclass: add task dependency between bundle_initramfs and package Ming Liu
2014-06-25  7:13 ` Ming Liu [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=53AA7684.7070105@windriver.com \
    --to=ming.liu@windriver.com \
    --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