From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Subject: Re: [PATCH] image_types.bbclass: use per-image dirs for extX.gz images generation
Date: Mon, 05 Sep 2011 20:24:15 +0100 [thread overview]
Message-ID: <1315250655.1243.9.camel@ted> (raw)
In-Reply-To: <1315078037-15012-1-git-send-email-dbaryshkov@gmail.com>
On Sat, 2011-09-03 at 23:27 +0400, Dmitry Eremin-Solenikov wrote:
> Currently image_types.bbclass uses deploy/images/${MACHINE}tpm.gz dir for
> temporary files when generating extX.gz images. This can lead to races
> and strange errors during image generation. To overcome this use
> deploy/images/${MACHINE}tpm.gz-${PN} dir for temporary files.
>
> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> ---
> meta/classes/image_types.bbclass | 32 ++++++++++++++++----------------
> 1 files changed, 16 insertions(+), 16 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-09-05 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-03 19:27 [PATCH] image_types.bbclass: use per-image dirs for extX.gz images generation Dmitry Eremin-Solenikov
2011-09-05 19:24 ` 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=1315250655.1243.9.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=dbaryshkov@gmail.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