From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] eglibc-2.15: Update SRCREV
Date: Fri, 23 Mar 2012 12:05:25 +0000 [thread overview]
Message-ID: <1332504325.9740.395.camel@ted> (raw)
In-Reply-To: <1332471418-31459-1-git-send-email-raj.khem@gmail.com>
On Thu, 2012-03-22 at 19:56 -0700, Khem Raj wrote:
> Get new patches and remove the one that got merged upstream
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> .../eglibc/eglibc-2.15/GLRO_dl_debug_mask.patch | 108 ++++++++++++++++++++
> .../eglibc-2.15/armv4-eabi-compile-fix.patch | 25 -----
> .../eglibc/eglibc-2.15/initgroups_keys.patch | 20 ++++
> meta/recipes-core/eglibc/eglibc_2.15.bb | 5 +-
> 4 files changed, 131 insertions(+), 27 deletions(-)
> create mode 100644 meta/recipes-core/eglibc/eglibc-2.15/GLRO_dl_debug_mask.patch
> delete mode 100644 meta/recipes-core/eglibc/eglibc-2.15/armv4-eabi-compile-fix.patch
> create mode 100644 meta/recipes-core/eglibc/eglibc-2.15/initgroups_keys.patch
Since 2.15 isn't the default I'm tempted to merge this despite the point
we're at in the release cycle. I'd like to give anyone using this the
opportunity to comment first though.
Cheers,
Richard
next prev parent reply other threads:[~2012-03-23 12:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 2:56 [PATCH 1/2] eglibc-2.15: Update SRCREV Khem Raj
2012-03-23 2:56 ` [PATCH 2/2] pixman: disable iwmmxt Khem Raj
2012-03-23 12:04 ` Richard Purdie
2012-03-23 12:08 ` Martin Jansa
2012-03-23 13:34 ` Khem Raj
2012-03-23 12:05 ` Richard Purdie [this message]
2012-03-23 13:17 ` [PATCH 1/2] eglibc-2.15: Update SRCREV Martin Jansa
2012-03-24 2:26 ` Martin Jansa
2012-03-28 14:15 ` Khem Raj
2012-03-28 14:33 ` Martin Jansa
2012-03-28 16:10 ` Khem Raj
2012-03-28 20:35 ` Martin Jansa
2012-04-04 21:11 ` Martin Jansa
2012-04-16 14:33 ` eglibc: shlib.lds:127: syntax error Was: " Martin Jansa
2012-04-17 14:31 ` Martin Jansa
2012-03-30 9:31 ` Martin Jansa
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=1332504325.9740.395.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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.