From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: Re: [PATCH 1/1] linux-libc-headers: use kernel-arch to set ARCH
Date: Thu, 21 Jun 2012 13:23:47 +0100 [thread overview]
Message-ID: <1340281427.1640.100.camel@ted> (raw)
In-Reply-To: <b6499cb8429671a360a1a1a0263f3f81c96ac5aa.1340202895.git.bruce.ashfield@windriver.com>
On Wed, 2012-06-20 at 10:54 -0400, Bruce Ashfield wrote:
> linux-libc-headers no longer needs its own ARCH mapping code,
> since the mapping done in kernel-arch works and we can
> consolidate all arch mapping code in a single place.
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
> .../linux-libc-headers/linux-libc-headers.inc | 30 ++-----------------
> 1 files changed, 4 insertions(+), 26 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-06-21 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 14:54 [PATCH 0/1] linux-libc-headers: use kernel-arch for ARCH Bruce Ashfield
2012-06-20 14:54 ` [PATCH 1/1] linux-libc-headers: use kernel-arch to set ARCH Bruce Ashfield
2012-06-21 12:23 ` Richard Purdie [this message]
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=1340281427.1640.100.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.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.