From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] linux-yocto: mips, -rt update and yocto-custom fix
Date: Mon, 1 Apr 2013 10:09:32 -0700 [thread overview]
Message-ID: <cover.1364835699.git.bruce.ashfield@windriver.com> (raw)
Richard,
Here are three small fixes that I've gathered up since pushing out the
last update to 3.8.x.
[PATCH 1/3] linux-yocto/3.8: update mips SA_RESTORER fix
During the 3.8.4 integration there was a build issue on MIPS due to
SA_RESTORER changes. A solution was put in place for mips, but it
didn't cover other impacted architectures.
This is a backport of the proposed fix for the next 3.8-stable,
since the full -stable might not be available in the right timeframe.
[PATCH 2/3] kernel-yocto: use KBRANCH as default build branch
commit 61001aa [kernel-yocto: respect SRC_URI modified branch selection]
changed branch processing such that a branch specified in the SRC_URI
would set the branch forced as the build branch.
This change broke compatibility with the yocto-bsp, linux-yocto-custom
based recipes. These recipes specify the branch to be built via KBRANCH,
but allow the fetcher to use master for keeping the repository up to
date. This means that no explicit branch is set in the SRC_URI and the
routines return the default branch of 'master', which is not what is
set in KBRANCH.
To support this case, we simply pass a default branch into the routine
returning the branch to build, and ensure that the default is KBRANCH
so if no branch is passed in the SRC_URI, KBRANCH is always built.
[YOCTO #4145]
[PATCH 3/3] linux-yocto-rt: integrate 3.8.4-rt2
Updating to 3.8.4-rt2 to fix the minor issues found with -rt1.
From the upstream commit log:
changes since v3.8.4-rt1:
- build fix for i915 (reported by "Luis Claudio R. Goncalves")
- build fix for fscache (reported by tglx)
- build fix for !RT (kernel/softirq.c did not compile)
- per-cpu rwsem fixed for RT (required only by uprobes so far)
- slub: delay the execution of the ->ctor() hook for newly created
objects. This lowers the worst case latencies.
* This also fixes a build issue reported by Tom Zanussi
Cheers,
Bruce
The following changes since commit 92aeb31341b28b193d616ab5cf38af1b9673e37d:
qemuimage-testlib: Fix quoting issue (2013-03-30 17:26:56 +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 (3):
linux-yocto/3.8: update mips SA_RESTORER fix
kernel-yocto: use KBRANCH as default build branch
linux-yocto-rt: integrate 3.8.4-rt2
meta/classes/kernel-yocto.bbclass | 11 ++++++-----
meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_3.8.bb | 12 ++++++------
3 files changed, 14 insertions(+), 13 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-04-01 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 17:09 Bruce Ashfield [this message]
2013-04-01 17:09 ` [PATCH 1/3] linux-yocto/3.8: update mips SA_RESTORER fix Bruce Ashfield
2013-04-01 17:09 ` [PATCH 2/3] kernel-yocto: use KBRANCH as default build branch Bruce Ashfield
2013-04-01 17:09 ` [PATCH 3/3] linux-yocto-rt: integrate 3.8.4-rt2 Bruce Ashfield
2013-04-01 19:24 ` [PATCH 0/3] linux-yocto: mips, -rt update and yocto-custom fix Khem Raj
2013-04-01 19:25 ` 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.1364835699.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