From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Tom, Darren Hart <dvhart@linux.intel.com>,
openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: linux-yocto: consolidated pull request
Date: Wed, 30 Nov 2011 19:36:46 -0500 [thread overview]
Message-ID: <4ED6CC1E.5040504@windriver.com> (raw)
Richard/Saul,
FYI: I can't get git-send email to work over the hotel wifi, so
I can't chain the patches to this email. If you want me to send
the patches separately, let me know. But for now, this is the
best I can do.
This pull request represents a collection of changes that were
part of yocto M1 work, and that set the stage for more updates
that will follow in the not too distant future.
I've bumped the 3.0 kernel to the 3.0.10 baseline (3.0.11 is
out, but not in this merge request) and updated our -rt patches
to the latest upstream -rt series.
This also drops the 2.6.34 recipe and leaves it to be supported
in previous releases. If there's somewhere else I should be
putting it, let me know and I'll put it there.
The kernel revision updates have been built and boot tested by
Tom and myself. And we have't seen any problems.
Also included in this are some changes to kernel tools that
prepare to move the kernel tools into the kernel tree itself.
They also move us to doing configuration auditing using the
merge_config script that Darren and John Stultz have been
working on.
And finally there's a small tweak to install the kernel tools
via Makefile in the package itself, something that I recall
Richard mentioning to me over 2 years ago a meeting .. so I thought
I'd finally get to it.
Cheers,
Brucedvhart@linux.intel.com
cc: Tom Zanussi <tom.zanussi@intel.com>
cc: Darren Hart <dvhart@linux.intel.com>
The following changes since commit d7cd934376ae1edaf7055ec635eb3c85fdbf58b3:
squashfs-tools: fix PR, those should start with 'r' (2011-11-30
23:37:44 +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 (7):
kern-tools: add pre_config and merge_config.sh to the list of tools
kernel-yocto: support allnoconfig base configuration
linux-yocto: remove 2.6.34 recipes
linux-yocto: v3.0.9 + enhancements
linux-yocto: v3.0.10 + rt27
linux-yocto: prefer in-tree tools to external ones
kern-tools: use Makefile provided install rules
meta/classes/kernel-yocto.bbclass | 24 +++++++++-
.../kern-tools/kern-tools-native_git.bb | 15 ++----
meta/recipes-kernel/linux/linux-yocto-rt_2.6.34.bb | 38 ---------------
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 8 ++--
meta/recipes-kernel/linux/linux-yocto_2.6.34.bb | 49
--------------------
meta/recipes-kernel/linux/linux-yocto_3.0.bb | 18 ++++----
6 files changed, 39 insertions(+), 113 deletions(-)
delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_2.6.34.bb
delete mode 100644 meta/recipes-kernel/linux/linux-yocto_2.6.34.bb
next reply other threads:[~2011-12-01 0:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 0:36 Bruce Ashfield [this message]
2011-12-01 5:25 ` linux-yocto: consolidated pull request Saul Wold
2011-12-01 17:11 ` Bruce Ashfield
2011-12-01 21:58 ` Bruce Ashfield
2011-12-02 0:47 ` Saul Wold
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=4ED6CC1E.5040504@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@intel.com \
/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