From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] linux-yocto: beagleboard, -rt and install fixes
Date: Thu, 14 Nov 2013 11:55:23 -0500 [thread overview]
Message-ID: <cover.1384447700.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
Here are two 3.10 kernel updates that I've had in my tree for a
while now, and a fix from this morning for the kernel install
issues being seen on the autobuilder.
The beagleboard changes are for [YOCTO #5211] and [YOCTO #5183],
which means working USB and ethernet.
The install fix addresses [YOCTO #5527], which means we can
avoid the install of vmlinux in a hard link situation.
Cheers,
Bruce
The following changes since commit ea92671d9823e3667d6ced7ac2af20f991da404d:
bitbake: cooker: replace "w" file opening mode with "a" mode (2013-11-12 17:01:37 +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.10: meta: ARM: OMAP3: Add USB PHY driver for
Beagleboard
linux-yocto-rt/3.10: fix ntp merge issue
kernel.bbclass: test for hardlinks before installing
meta/classes/kernel.bbclass | 6 +++++-
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 3 +--
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 2 +-
4 files changed, 10 insertions(+), 7 deletions(-)
--
1.8.1.2
next reply other threads:[~2013-11-14 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 16:55 Bruce Ashfield [this message]
2013-11-14 16:55 ` [PATCH 1/3] linux-yocto/3.10: meta: ARM: OMAP3: Add USB PHY driver for Beagleboard Bruce Ashfield
2013-11-14 19:35 ` Bruce Ashfield
2013-11-14 16:55 ` [PATCH 2/3] linux-yocto-rt/3.10: fix ntp merge issue Bruce Ashfield
2013-11-14 16:55 ` [PATCH 3/3] kernel.bbclass: test for hardlinks before installing 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.1384447700.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.