From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] linux-yocto/3.10: M4/rc fixes
Date: Wed, 4 Sep 2013 22:20:21 -0400 [thread overview]
Message-ID: <cover.1378347409.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
Here are my pending m4/rc3 fixes for the 3.10 kernel. I know you are most
interested in patch 3/3, but patches 1 and 2 have already been staged,
merged and pushed to the linux-yocto tree, since they were also destined
for M4, reverting them makes a horrible mess of history, and reverts
merge commits, so that's a really bad idea.
Anyway, here are the three patches. With these, we have a building yaffs2,
CVE and -stable fixes (prep for our ssh issues) and finally a working
mips graphical login.
Cheers,
Bruce
[YOCTO #5095]
The following changes since commit f41b7a7d4d0463a0dfafe6621d01680b81798019:
bitbake: hob: remove PACKAGE_INSTALL variable setting from hob (2013-09-04 14:18:49 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel-hot-fixes
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-hot-fixes
Bruce Ashfield (3):
linux-yocto/3.10: fix YAFFS2 build issues
linux-yocto/3.10: update to v3.10.10
qemumips: fix keyboard entry in graphical boots
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 16 ++++++++--------
3 files changed, 13 insertions(+), 13 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-09-05 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 2:20 Bruce Ashfield [this message]
2013-09-05 2:20 ` [PATCH 1/3] linux-yocto/3.10: fix YAFFS2 build issues Bruce Ashfield
2013-09-05 2:20 ` [PATCH 2/3] linux-yocto/3.10: update to v3.10.10 Bruce Ashfield
2013-09-05 2:20 ` [PATCH 3/3] qemumips: fix keyboard entry in graphical boots 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.1378347409.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 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.