From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] kernel-yocto: consolidated pull request
Date: Thu, 30 May 2013 23:28:44 -0400 [thread overview]
Message-ID: <cover.1369970703.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
While I continue to battle with gcc 4.8, I've got a collection of other fixes
that don't need to wait. Here's part of those pending changes.
- Remove the yocto 3.2 kernel, early in the Yocto 1.5 cycle as promised
- Fix the reported issues with linux-yocto-custom recipes by restricting
NFSD kernel feature requirements to full linux-yocto kernels
- Refresh the 3.4 and 3.8 kernels with stable updates
- Fix a kernel feature processing bug reported with some of the Intel BSPs
Cheers,
Bruce
The following changes since commit 647db80298da0a8da212449fdd80d318773eacef:
hicolor-icon-theme: keep inherited dependencies and switch to gnomebase (2013-05-30 22:31:37 +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 (4):
linux-yocto: remove 3.2 kernel recipes
qemu*: restrict NFSD to linux-yocto only
linux-yocto: v3.8.13 and v3.4.46
kern-tools: expand kernel features that point to a directory name
meta/conf/machine/include/qemu.inc | 2 +-
.../kern-tools/kern-tools-native_git.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb | 29 -----------------
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++---
meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb | 8 ++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb | 26 ---------------
meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_3.8.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto_3.2.bb | 33 --------------------
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 +++++-----
meta/recipes-kernel/linux/linux-yocto_3.8.bb | 17 +++++-----
11 files changed, 32 insertions(+), 121 deletions(-)
delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
delete mode 100644 meta/recipes-kernel/linux/linux-yocto_3.2.bb
--
1.7.10.4
next reply other threads:[~2013-05-31 3:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 3:28 Bruce Ashfield [this message]
2013-05-31 3:28 ` [PATCH 1/4] linux-yocto: remove 3.2 kernel recipes Bruce Ashfield
2013-05-31 3:28 ` [PATCH 2/4] qemu*: restrict NFSD to linux-yocto only Bruce Ashfield
2013-05-31 3:28 ` [PATCH 3/4] linux-yocto: v3.8.13 and v3.4.46 Bruce Ashfield
2013-05-31 3:28 ` [PATCH 4/4] kern-tools: expand kernel features that point to a directory name Bruce Ashfield
2013-05-31 6:14 ` [PATCH 0/4] kernel-yocto: consolidated pull request Saul Wold
2013-05-31 7:07 ` Richard Purdie
2013-05-31 12:29 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2015-03-02 21:36 Bruce Ashfield
2016-12-02 21:09 Bruce Ashfield
2016-12-06 19:32 ` Trevor Woerner
2019-12-30 3:07 bruce.ashfield
2020-03-04 14:55 bruce.ashfield
2020-08-03 12:30 Bruce Ashfield
2025-04-10 18:55 bruce.ashfield
2025-04-10 20:24 ` Richard Purdie
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.1369970703.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