From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ChenQi <Qi.Chen@windriver.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kernel/rm_work: Improve interaction
Date: Wed, 20 May 2015 13:05:31 +0100 [thread overview]
Message-ID: <1432123531.28910.56.camel@linuxfoundation.org> (raw)
In-Reply-To: <555C2326.90207@windriver.com>
On Wed, 2015-05-20 at 14:01 +0800, ChenQi wrote:
> I've observed a side effect of this patch.
> The problem is sstate reuse.
>
> Steps to reproduce:
> 1) bitbake core-image-minimal
> 2) Change TMPDIR in local.conf
> TMPDIR = "${TOPDIR}/tmp-test"
> 3) bitbake core-image-minimal
>
> In theory, sstate objects are all reused in step 3. But currently the
> do_populate_sysroot sstate object of the kernel is not reused. In
> addition, other kernel tasks like do_fetch, do_patch, do_compile, etc,
> are rerun.
Well spotted, I've sent a patch out for this.
Cheers,
Richard
prev parent reply other threads:[~2015-05-20 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 9:31 [PATCH] kernel/rm_work: Improve interaction Richard Purdie
2015-05-20 6:01 ` ChenQi
2015-05-20 12:05 ` 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=1432123531.28910.56.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Qi.Chen@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