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 0/1] linux-yocto: update SRCREVs
Date: Tue, 31 May 2011 08:53:55 +0100 [thread overview]
Message-ID: <1306828435.27470.333.camel@rex> (raw)
In-Reply-To: <cover.1306777062.git.bruce.ashfield@windriver.com>
On Mon, 2011-05-30 at 13:41 -0400, Bruce Ashfield wrote:
> Richard/Saul,
>
> Just updating the linux-yocto SRCREVs to pickup the Romley
> changes and meta cleanup from TomZ. There's also a config update
> for the routerstation pro to enable watchdog support to fix
> yocto bug 1111.
>
[...]
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (1):
> linux-yocto: update meta SRCREV
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-05-31 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 17:41 [PATCH 0/1] linux-yocto: update SRCREVs Bruce Ashfield
2011-05-30 17:41 ` [PATCH 1/1] linux-yocto: update meta SRCREV Bruce Ashfield
2011-05-31 7:53 ` 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=1306828435.27470.333.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