From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] linux-yocto/4.1/4.4: -stable and configuration updates
Date: Sat, 20 Aug 2016 00:30:33 -0400 [thread overview]
Message-ID: <cover.1471667296.git.bruce.ashfield@windriver.com> (raw)
Hi all,
Here are the next set of -stable updates for the linux-yocto kernels. These
contain some CVE fixes that folks have been asking about, so I've queued
and sent them right away.
I built and ran qemuppc against 4.1.30 and wasn't able to see any instability,
but will continue to run stress tests.
4.4.18 was built and booted against qemu*
Cheers,
Bruce
The following changes since commit f038f069977170e323c9c6884c69e0b9e1cf1c6f:
local.conf.sample: Disable ARM and PPC due to prelink test case failures (2016-08-19 10:23:55 +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/4.1/4.4: -stable updates and configuration changes
linux-yocto/4.4: fix configuration warnings
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_4.1.bb | 20 ++++++++++----------
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 20 ++++++++++----------
6 files changed, 32 insertions(+), 32 deletions(-)
--
2.5.0
next reply other threads:[~2016-08-20 4:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-20 4:30 Bruce Ashfield [this message]
2016-08-20 4:30 ` [PATCH 1/2] linux-yocto/4.1/4.4: -stable updates and configuration changes Bruce Ashfield
2016-08-20 4:30 ` [PATCH 2/2] linux-yocto/4.4: fix configuration warnings 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.1471667296.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.