Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: Re: [PATCH 1/1] linux-yocto: update SRCREVs
Date: Wed, 27 Jul 2011 16:12:36 +0100	[thread overview]
Message-ID: <1311779556.2344.386.camel@rex> (raw)
In-Reply-To: <35a96b8d01511443b0743cca3543a4cdc007cff2.1311738733.git.bruce.ashfield@windriver.com>

On Tue, 2011-07-26 at 23:55 -0400, Bruce Ashfield wrote:
> Updating the linux-yocto SRCREVs to pickup changes from the
> continuing uprev to korg 3.0. With this set of update, the
> meta/feature audits are complete.
> 
> qemumips and qemuppc are fixed with this update and can now
> boot to a prompt.
> 
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>

Merged to master, thanks.

Richard




      reply	other threads:[~2011-07-27 15:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27  3:55 [PATCH 0/1] linux-yocto: update cfgs and enable qemuppc/mips Bruce Ashfield
2011-07-27  3:55 ` [PATCH 1/1] linux-yocto: update SRCREVs Bruce Ashfield
2011-07-27 15:12   ` 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=1311779556.2344.386.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=saul.wold@intel.com \
    /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