From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] linux-yocto: -stable, -rt updates and 4.8 removal
Date: Tue, 28 Mar 2017 08:58:02 -0400 [thread overview]
Message-ID: <cover.1490705726.git.bruce.ashfield@windriver.com> (raw)
Hi all,
These are updates to the 4.4, 4.9 and 4.10 linux-yocto kernel trees to
the latest -stable and -rt releases.
Nothing particular ground breaking here, but they are the usual set of
CVE and bug fixes. Everything built and booted fine for me.
I'm also removing the 4.8 linux-yocto recipe from master, since we are
adding 4.10 for this release. I'll still be doing updates to 4.8, just
not sending SRCREV updates to master.
Cheers,
Bruce
The following changes since commit 49c2df5652d25e6e9b2a4976658ab9bb17fe6694:
meta-yocto-bsp: Remove superfluous OVERRIDES in machine conf files (2017-03-22 11:35:23 +0000)
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 (5):
linux-yocto/4.10: update to v4.10.5
linux-yocto/4.9: update to v4.9.17
linux-yocto/4.4: update to v4.4.56
linux-yocto/4.9: integrate 4.9-rt12
linux-yocto: drop 4.8 recipes
meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb | 6 +--
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 6 +--
meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb | 38 -------------------
meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb | 6 +--
meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb | 6 +--
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 6 +--
meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb | 25 ------------
meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb | 6 +--
meta/recipes-kernel/linux/linux-yocto_4.10.bb | 20 +++++-----
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 20 +++++-----
meta/recipes-kernel/linux/linux-yocto_4.8.bb | 44 ----------------------
meta/recipes-kernel/linux/linux-yocto_4.9.bb | 20 +++++-----
12 files changed, 48 insertions(+), 155 deletions(-)
delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb
delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb
delete mode 100644 meta/recipes-kernel/linux/linux-yocto_4.8.bb
--
2.5.0
next reply other threads:[~2017-03-28 12:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 12:58 Bruce Ashfield [this message]
2017-03-28 12:58 ` [PATCH 1/5] linux-yocto/4.10: update to v4.10.5 Bruce Ashfield
2017-03-28 12:58 ` [PATCH 2/5] linux-yocto/4.9: update to v4.9.17 Bruce Ashfield
2017-03-28 12:58 ` [PATCH 3/5] linux-yocto/4.4: update to v4.4.56 Bruce Ashfield
2017-03-28 12:58 ` [PATCH 4/5] linux-yocto/4.9: integrate 4.9-rt12 Bruce Ashfield
2017-03-28 12:58 ` [PATCH 5/5] linux-yocto: drop 4.8 recipes Bruce Ashfield
2017-04-04 7:56 ` Martin Jansa
2017-04-04 7:59 ` Bruce Ashfield
2017-04-04 8:02 ` [PATCH] x86-base.inc, qemuarm.conf: prefer 4.10 version of linux-yocto Martin Jansa
2017-04-04 9:48 ` Burton, Ross
2017-04-04 17:10 ` Martin Jansa
2017-04-05 12:13 ` Bruce Ashfield
2017-04-04 9:02 ` ✗ patchtest: failure for linux-yocto: -stable, -rt updates and 4.8 removal (rev2) Patchwork
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.1490705726.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox