From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] linux-yocto/3.10: LTSI, -stable, CVE and systemd
Date: Fri, 14 Feb 2014 14:13:53 -0500 [thread overview]
Message-ID: <cover.1392404866.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
Here are my queued 3.10 kernel changes that have been simmering and under
test. Everything is sane for my builds.
Cheers,
Bruce
The following changes since commit ee151ed6bc16312733c67b91bbf65959309b640d:
lib/oe/rootfs.py: fix RPM multilib issue (2014-02-13 12:06:01 +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 (4):
linux-yocto/3.10: update to v3.10.28
linux-yocto/3.10: arbitrary write with CONFIG_X86_X32 (CVE-2014-0038)
linux-yocto/3.10: add minnow-io feature to LTSI
linux-yocto/3.10: enable CONFIG_FHANDLE for standard and preempt-rt
kernels
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 8 ++++----
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 18 +++++++++---------
3 files changed, 16 insertions(+), 16 deletions(-)
--
1.8.1.2
next reply other threads:[~2014-02-14 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 19:13 Bruce Ashfield [this message]
2014-02-14 19:13 ` [PATCH 1/4] linux-yocto/3.10: update to v3.10.28 Bruce Ashfield
2014-02-14 19:13 ` [PATCH 2/4] linux-yocto/3.10: arbitrary write with CONFIG_X86_X32 (CVE-2014-0038) Bruce Ashfield
2014-02-14 19:13 ` [PATCH 3/4] linux-yocto/3.10: add minnow-io feature to LTSI Bruce Ashfield
2014-02-14 19:13 ` [PATCH 4/4] linux-yocto/3.10: enable CONFIG_FHANDLE for standard and preempt-rt kernels 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.1392404866.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.