From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] linux-yocto: consolidated update
Date: Thu, 13 Sep 2012 15:34:35 -0400 [thread overview]
Message-ID: <cover.1347564407.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
A small ``consolidated'' update this time. Two fixes, one to the build/tools,
one meta branch update for KVM guests.
The tools fix is something that I've been wanting to get to for a month
now .. and I finally did. Matthew Foster reported the strange messages
when working with linux-yocto-custom. It is now fixed, and no more nasty
looking messages. The details of the messages and fix are in the patch.
The second meta/config patch is to embed some fragments for use by a
KVM guest. These will be used by other updates to the tools/scripts
to follow.
Cheers,
Bruce
The following changes since commit 7401ed019196313a7ae7cab0b9f3820356cfee29:
Update to upstream_tracking.inc (2012-09-12 17:56:58 +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 (2):
kernel-yocto: fix kernel configuration audit for custom yocto kernels
linux-yocto: virtio and KVM guest configuration
meta/classes/kernel-yocto.bbclass | 7 ++++++-
.../kern-tools/kern-tools-native_git.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_3.4.bb | 2 +-
4 files changed, 9 insertions(+), 4 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-09-13 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 19:34 Bruce Ashfield [this message]
2012-09-13 19:34 ` [PATCH 1/2] kernel-yocto: fix kernel configuration audit for custom yocto kernels Bruce Ashfield
2012-09-13 19:34 ` [PATCH 2/2] linux-yocto: virtio and KVM guest configuration Bruce Ashfield
2012-09-14 15:56 ` [PATCH 0/2] linux-yocto: consolidated update Saul Wold
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.1347564407.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