All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: yocto@yoctoproject.org, poky@yoctoproject.org, saul.wold@intel.com
Subject: [PATCH 0/2] linux-libc-headers-yocto: 3.4 and cleanups
Date: Fri, 22 Jun 2012 12:04:44 -0400	[thread overview]
Message-ID: <cover.1340380930.git.bruce.ashfield@windriver.com> (raw)

Richard/Saul,

There aren't that many users of this recipe, but for those cases
that we need it .. this needed a bit of love. I've made the same
fix that went into the oe-core libc-headers and then bumped this
recipe to the 3.4 standard/base for headers. With recent updates
to the tools, there were parts of this recipe that could be removed,
and they are now gone!

Cheers,

Bruce

The following changes since commit b876f42821383bf0069ee49b607ba06614417fba:
  Bogdan Marinescu (1):
        guile: fix compilation on MIPS/PPC

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/libc-headers
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/libc-headers

Bruce Ashfield (2):
  linux-libc-headers-yocto: use kernel-arch to set ARCH
  linux-libc-headers-yocto: update to v3.4 and remove unecessary code

 .../linux-libc-headers-yocto_git.bb                |   45 ++++----------------
 1 files changed, 8 insertions(+), 37 deletions(-)



             reply	other threads:[~2012-06-22 15:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 16:04 Bruce Ashfield [this message]
2012-06-22 16:04 ` [PATCH 1/2] linux-libc-headers-yocto: use kernel-arch to set ARCH Bruce Ashfield
2012-06-22 16:04 ` [PATCH 2/2] linux-libc-headers-yocto: update to v3.4 and remove unecessary code 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.1340380930.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=poky@yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.org \
    --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.