From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: simarpreet.singh@windriver.com, poky@yoctoproject.org
Subject: [PATCH 0/1] meta-yocto-bsp: update 3.4 and 3.8 SRCREVs
Date: Sat, 6 Jul 2013 22:13:19 -0400 [thread overview]
Message-ID: <cover.1373162883.git.bruce.ashfield@windriver.com> (raw)
Saul,
Updating the SRCREVs for the reference boards for both the 3.4
and 3.8 kernels.
The 3.4 change is updating to the 3.4.52 stable version, which
is the same update that the qemu* machines got for oe-core.
The 3.8 change addresses our routerstationpro boot issue. We
somehow managed to update its preferred kernel to 3.8, but not
update the SRCREVs. Simar managed to track down the missing change,
and I've gone ahead and updated all the reference boards (even
if they are not all currently setting their preferred kernel
to 3.8. I'll take care of that preferred kernel setting shortly
as well, but there's no reason to hold on this).
With this YOCTO #4566, should be addressed.
Cheers,
Bruce
The following changes since commit dd626321f93b7d145b05bedd54eba9d1947a1d6c:
linux-yocto/3.4: update to v3.4.52 (2013-07-05 20:51:26 -0400)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel-yocto
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto
Bruce Ashfield (1):
meta-yocto-bsp: update reference board SRCREVs
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.4.bbappend | 8 ++++----
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.8.bbappend | 8 ++++----
2 files changed, 8 insertions(+), 8 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-07-07 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 2:13 Bruce Ashfield [this message]
2013-07-07 2:13 ` [PATCH 1/1] meta-yocto-bsp: update reference board SRCREVs Bruce Ashfield
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.1373162883.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=simarpreet.singh@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.