From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Fix prelink to avoid first boot script
Date: Wed, 29 Jun 2011 14:36:15 +0100 [thread overview]
Message-ID: <1309354575.20015.376.camel@rex> (raw)
In-Reply-To: <cover.1309311666.git.mark.hatle@windriver.com>
On Tue, 2011-06-28 at 20:42 -0500, Mark Hatle wrote:
> In most cases the user will have the image-prelink enabled, which will
> prelink the target image at image creation time. If this is enabled
> we want to avoid prelinking at first boot. We do this by setting the
> script exit status to '0' if we detect we're on the host.
>
> Also fixes a small bug found in sstate.bbclass: do_cleansstate
>
> The following changes since commit 8a5c20417d4d6bee6dd0bcdbeb8d4f9e0696a216:
>
> [PATCH] u-boot-mkimage: bump version to 2011.03 (2011-06-28 17:13:12 +0100)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib mhatle/prelink
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/prelink
>
> Mark Hatle (2):
> sstate.bbclass: Fix an issue if the config changes
> prelink_git.bb: Only block the postinst script when no image-prelink
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-06-29 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 1:42 [PATCH 0/2] Fix prelink to avoid first boot script Mark Hatle
2011-06-29 1:42 ` [PATCH 1/2] sstate.bbclass: Fix an issue if the config changes Mark Hatle
2011-06-29 1:42 ` [PATCH 2/2] prelink_git.bb: Only block the postinst script when no image-prelink Mark Hatle
2011-06-29 11:20 ` Phil Blundell
2011-06-29 11:20 ` Phil Blundell
2011-06-29 13:36 ` 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=1309354575.20015.376.camel@rex \
--to=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox