From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] linux-yocto/3.10/3.14: SRCREV updates
Date: Thu, 18 Sep 2014 11:32:26 -0400 [thread overview]
Message-ID: <cover.1411053678.git.bruce.ashfield@windriver.com> (raw)
Hi all,
Here are the final -stable refresh update for 3.10 and 3.14 for the 1.7
release.
I've done build and boot testing for the arches on qemu machines, both for
standard and -rt. That being said, feeding it to a round of automated build
testing would be ideal, since I can't cover every single config and case.
I'll follow up with h/w reference board updates, which are staying on
3.14 for this release, so they need the new SRCREVs as well.
Cheers,
Bruce
The following changes since commit 280b6d0011f101e7a8edabd34c265b37a2f791ed:
sstatesig: fix overrides behaviour to remove SIGGEN_LOCKEDSIGS_i586 (2014-09-17 22:00:26 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (2):
linux-yocto/3.10: update to v3.10.54 and -rt55
linux-yocto/3.14: update to v3.14.18 and -rt9
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 8 ++++----
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb | 8 ++++----
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 18 +++++++++---------
meta/recipes-kernel/linux/linux-yocto_3.14.bb | 18 +++++++++---------
6 files changed, 32 insertions(+), 32 deletions(-)
--
1.8.1.2
next reply other threads:[~2014-09-18 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 15:32 Bruce Ashfield [this message]
2014-09-18 15:32 ` [PATCH 1/2] linux-yocto/3.10: update to v3.10.54 and -rt55 Bruce Ashfield
2014-09-18 15:32 ` [PATCH 2/2] linux-yocto/3.14: update to v3.14.18 and -rt9 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.1411053678.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 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.