All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: Martin Jansa
	<martin.jansa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] kernel.bbclass: Delay rm_work to run after do_bundle_initramfs
Date: Thu, 07 Nov 2013 22:26:28 +0000	[thread overview]
Message-ID: <1383863188.6271.273.camel@ted> (raw)
In-Reply-To: <lyob5wb669.fsf@ensc-virt.intern.sigma-chemnitz.de>

On Thu, 2013-11-07 at 16:08 +0100, Enrico Scholz wrote:
> Martin Jansa <martin.jansa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> writes:
> 
> > Why not add "before" param to addtask?
> >
> > addtask bundle_initramfs after do_compile before do_build
> >
> > could do the trick
> 
> no; due to
> 
>   do_bundle_initramfs[nostamp] = "1"
> 
> a (non-initramfs) kernel will be rebuilt everytime although nothing has
> been changed.  The initramfs related tasks should be executed only when
> an initramfs is really used.

There is no good reason to have this as a nostamp task any more. With
the checksums on the stamp files, we have reliable image generation now.

Cheers,

Richard



      reply	other threads:[~2013-11-07 22:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31  1:24 [PATCH] kernel.bbclass: Delay rm_work to run after do_bundle_initramfs Xufeng Zhang
2013-10-31  8:26 ` Martin Jansa
2013-11-01  1:10   ` Xufeng Zhang
2013-11-07 15:08   ` Enrico Scholz
2013-11-07 22:26     ` 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=1383863188.6271.273.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=enrico.scholz@sigma-chemnitz.de \
    --cc=martin.jansa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --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 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.