From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: dvhart@linux.intel.com, openembedded-core@lists.openembedded.org,
saul.wold@intel.com
Subject: [PATCH 0/3] linux-yocto: consolidated pull request
Date: Mon, 27 Feb 2012 14:34:13 -0500 [thread overview]
Message-ID: <cover.1330371008.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
Here's a consolidated pull reqeset for the some kernel items.
- a bump of 3.0 to 3.0.22
- a bump of 3.2 to 3.2.7
- A fix for yocto 2032
You can cherry pick the bug fix by itself. As for the version
updates, I've built and booted them on my development machine
and on a clean machine, so they are safe for everything that
I've been able to test.
cc: Darren Hart <dvhart@linux.intel.com>
Cheers,
Bruce
The following changes since commit f420fb3de1f588a51dd6009452c7836903fa9158:
Richard Purdie (1):
glib-2.0: Disable fam, we don't depend on it
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 (3):
linux-yocto: update 3.0 kernel to v3.0.22
linux-yocto: update 3.2 kernel to v3.2.7
linux-yocto: allow non-branched repositories to check out
meta/classes/kernel-yocto.bbclass | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 8 ++++----
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb | 9 +++++----
meta/recipes-kernel/linux/linux-yocto-tiny_3.0.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_3.0.bb | 18 +++++++++---------
meta/recipes-kernel/linux/linux-yocto_3.2.bb | 19 ++++++++++---------
6 files changed, 32 insertions(+), 30 deletions(-)
next reply other threads:[~2012-02-27 19:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 19:34 Bruce Ashfield [this message]
2012-02-27 19:34 ` [PATCH 1/3] linux-yocto: update 3.0 kernel to v3.0.22 Bruce Ashfield
2012-02-27 19:34 ` [PATCH 2/3] linux-yocto: update 3.2 kernel to v3.2.7 Bruce Ashfield
2012-02-27 23:23 ` Saul Wold
2012-02-28 0:02 ` Darren Hart
2012-02-27 19:34 ` [PATCH 3/3] linux-yocto: allow non-branched repositories to check out Bruce Ashfield
2012-02-28 18:41 ` [PATCH 0/3] linux-yocto: consolidated pull request Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2020-03-22 1:18 Bruce Ashfield
2019-02-09 18:37 bruce.ashfield
2019-02-06 19:50 bruce.ashfield
2019-01-21 17:26 Bruce Ashfield
2019-01-12 18:12 Bruce Ashfield
2018-04-09 15:16 Bruce Ashfield
2016-09-20 15:16 Bruce Ashfield
2016-06-06 8:15 Bruce Ashfield
2016-05-24 15:53 Bruce Ashfield
2013-11-26 17:33 Bruce Ashfield
2013-09-18 18:24 Bruce Ashfield
2012-12-03 20:49 Bruce Ashfield
2012-08-27 4:49 Bruce Ashfield
2012-08-28 14:22 ` Saul Wold
2012-08-29 7:58 ` Bruce Ashfield
2012-03-05 4:01 Bruce Ashfield
2012-03-13 15:54 ` Saul Wold
2012-01-04 20:12 Bruce Ashfield
2011-12-08 17:11 Bruce Ashfield
2011-09-14 18:11 Bruce Ashfield
2011-09-15 17:37 ` Saul Wold
2011-09-03 3:03 Bruce Ashfield
2011-09-05 19:26 ` Richard Purdie
2011-08-19 5:20 Bruce Ashfield
2011-08-20 5:08 ` Bruce Ashfield
2011-08-15 20:24 Bruce Ashfield
2011-08-22 22:37 ` Saul Wold
2011-05-09 18:34 Bruce Ashfield
2011-05-10 17:53 ` Saul Wold
2011-05-05 4:53 Bruce Ashfield
2011-01-17 21:57 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.1330371008.git.bruce.ashfield@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 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.