From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: [PATCH 0/3] linux-yocto: consolidated pull request
Date: Mon, 27 Aug 2012 00:49:17 -0400 [thread overview]
Message-ID: <cover.1346042224.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
Here's some changes that I've staged over the past week or so,
everything checks out here, and there are some good changes in
this set of -stable updates, and and the linker fix from Khem.
I've also got a small tools fix here as well, that was needed
for some of the yocto-bsp builds. I think we've worked through
most of them now, and everything is looking good.
Cheers,
Bruce
cc: Khem Raj <raj.khem@gmail.com>
cc: Tom Zanussi <tom.zanussi@intel.com>
The following changes since commit b4c5725af4cd85d5644f0373e2674e903c4eab2b:
yocto-bsp: add missing xserver-xf86-config .bbappend for qemu (2012-08-25 14:47:07 +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 (3):
kern-tools: fix forced branching
linux-yocto/3.4: v3.4.9, unionfs, perf and configuration changes
linux-yocto/3.2/3.4: arm: Fix linking errors with binutils 2.23
.../kern-tools/kern-tools-native_git.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 8 ++++----
meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_3.2.bb | 12 ++++++------
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 16 ++++++++--------
6 files changed, 22 insertions(+), 22 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-08-27 5:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 4:49 Bruce Ashfield [this message]
2012-08-27 4:49 ` [PATCH 1/3] kern-tools: fix forced branching Bruce Ashfield
2012-08-27 4:49 ` [PATCH 2/3] linux-yocto/3.4: v3.4.9, unionfs, perf and configuration changes Bruce Ashfield
2012-08-27 4:49 ` [PATCH 3/3] linux-yocto/3.2/3.4: arm: Fix linking errors with binutils 2.23 Bruce Ashfield
2012-08-28 14:22 ` [PATCH 0/3] linux-yocto: consolidated pull request Saul Wold
2012-08-29 7:58 ` Bruce Ashfield
-- 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-03-05 4:01 Bruce Ashfield
2012-03-13 15:54 ` Saul Wold
2012-02-27 19:34 Bruce Ashfield
2012-02-28 18:41 ` 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.1346042224.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.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.