From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: [PATCH/PULL 0/1] linux-yocto: update meta SRCREV
Date: Mon, 16 May 2011 15:48:19 -0400 [thread overview]
Message-ID: <cover.1305575014.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
Just a quick update of the linux-yocto SRCREV to pickup a
couple of x86 BSP changes that have been done recently, and
will be used in some upcoming development work.
cc: Tom Zanussi <tom.zanussi@intel.com>
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/emgd
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/emgd
Thanks,
Bruce Ashfield <bruce.ashfield@windriver.com>
---
Bruce Ashfield (1):
linux-yocto: update meta SRCREV
meta/recipes-kernel/linux/linux-yocto_git.bb | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
next reply other threads:[~2011-05-16 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 19:48 Bruce Ashfield [this message]
2011-05-16 19:48 ` [PATCH 1/1] linux-yocto: update meta SRCREV Bruce Ashfield
2011-05-17 18:24 ` [PATCH/PULL 0/1] " Saul Wold
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=cover.1305575014.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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