From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: dvhart@linux.intel.com, openembedded-core@lists.openembedded.org,
saul.wold@intel.com
Subject: [PATCH 0/1] linux-libc-headers-yocto: bump to 3.22 and fix validation
Date: Wed, 29 Feb 2012 21:27:06 -0500 [thread overview]
Message-ID: <cover.1330568367.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
This is a second fix for YOCTO 2032. BSPs that want the bleeding edge kernel
headers were still seeing some branch validation errors with the yocto libc
headers recipe.
There were two reasons:
- we were pointing at an old tree, which introduced some branch naming
issues
- there were some new routines in the base yocto kernel class that
should just be overriden
This change bumps the linux-yocto based libc headers to v3.2.8, indicates
that 'standard/base' should be used for those headers and stubs out
validation and configuration tasks we don't need for header generation.
Both Darren and myself have tested this one.
cc: Darren Hart <dvhart@linux.intel.com>
Cheers,
Bruce
The following changes since commit 8f07bdc0a42dd7a7c3acf5d1b13220dbc98c8017:
Richard Purdie (1):
image_types_uboot: Update to work after recent image_types changes
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/yocto-libc-headers
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/yocto-libc-headers
Bruce Ashfield (1):
linux-libc-headers-yocto: bump to v3.2.8
.../linux-libc-headers-yocto_git.bb | 29 +++++++++++++-------
1 files changed, 19 insertions(+), 10 deletions(-)
next reply other threads:[~2012-03-01 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 2:27 Bruce Ashfield [this message]
2012-03-01 2:27 ` [PATCH 1/1] linux-libc-headers-yocto: bump to v3.2.8 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.1330568367.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@intel.com \
/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.