From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: rpurdie@linux.intel.com
Cc: yocto@yoctoproject.org, poky@yoctoproject.org, saul.wold@intel.com
Subject: [PATCH 0/2] linux-yocto: 2.6.37-rc7 & bsp branch fixups
Date: Tue, 28 Dec 2010 01:49:12 -0500 [thread overview]
Message-ID: <cover.1293518497.git.bruce.ashfield@windriver.com> (raw)
The first patch of this pull request updates the BSP branches
to 2.6.37-rc7 (all qemu targets have been built and booted).
The second patch is an update to the handling of KMACHINE as it
maps to the branch that we should be building for a BSP. During
some investigation around the igep0020 and building it on top of
the beagle board branches, the kernel branch was coming through
processing as UNDEFINED. This lead to errors. I tracked it down
to the non-override variable being used in the python processing.
Patch 2/2 updates the processing to check overrrides and then
fall back. With this, I was able to build an igep0020 on top of
the 2.6.37-rc7 beagle board kernel branches.
Cheers,
Bruce
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Thanks,
Bruce Ashfield <bruce.ashfield@windriver.com>
---
Bruce Ashfield (2):
yocto-kernel: fix kmachine to deal with overrides
yocto/meta: update to 2.6.37-rc7
meta/classes/kernel-yocto.bbclass | 7 +++++--
.../conf/distro/include/poky-default-revisions.inc | 20 ++++++++++----------
2 files changed, 15 insertions(+), 12 deletions(-)
next reply other threads:[~2010-12-28 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 6:49 Bruce Ashfield [this message]
2010-12-28 6:49 ` [PATCH 1/2] yocto-kernel: fix kmachine to deal with overrides Bruce Ashfield
2010-12-28 6:49 ` [PATCH 2/2] yocto/meta: update to 2.6.37-rc7 Bruce Ashfield
2010-12-29 20:24 ` [PATCH 0/2] linux-yocto: 2.6.37-rc7 & bsp branch fixups Saul Wold
2010-12-29 20:24 ` [poky] " 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.1293518497.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=poky@yoctoproject.org \
--cc=rpurdie@linux.intel.com \
--cc=saul.wold@intel.com \
--cc=yocto@yoctoproject.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.