From: Phil Blundell <pb@pbcl.net>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] glibc: Upgrade to 2.25
Date: Fri, 13 Jan 2017 20:20:39 +0000 [thread overview]
Message-ID: <1484338839.3966.89.camel@pbcl.net> (raw)
In-Reply-To: <3441a3d4-be4e-1f6a-6a4b-9b556796d83d@gmail.com>
On Fri, 2017-01-13 at 10:52 -0800, Khem Raj wrote:
>
> I have sent a patchset with IFUNC change reverted for now until its
> fixed.
Yeah, I saw that. But in light of recent developments it seems like it
might be better to revert the earlier NPTL patch that apparently
introduced the real problem.
p.
next prev parent reply other threads:[~2017-01-13 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 3:51 [PATCH 1/2] grub-git: Upgrade to tip of master and fix with glibc 2.25 Khem Raj
2017-01-11 3:51 ` [PATCH 2/2] glibc: Upgrade to 2.25 Khem Raj
2017-01-11 12:19 ` Burton, Ross
2017-01-11 15:56 ` Phil Blundell
2017-01-11 16:21 ` Khem Raj
2017-01-11 16:54 ` Phil Blundell
2017-01-13 18:45 ` Phil Blundell
2017-01-13 18:52 ` Khem Raj
2017-01-13 20:20 ` Phil Blundell [this message]
2017-01-11 15:44 ` Phil Blundell
2017-01-11 15:53 ` Burton, Ross
2017-01-11 16:09 ` Khem Raj
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=1484338839.3966.89.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox