From: Carlos O'Donell <carlos@redhat.com>
To: Szabolcs Nagy <Szabolcs.Nagy@arm.com>,
Siddhesh Poyarekar <siddhesh@gotplt.org>,
GLIBC Devel <libc-alpha@sourceware.org>
Cc: nd <nd@arm.com>, Feng Xue <fxue@os.amperecomputing.com>
Subject: Re: glibc 2.29 - Winter is coming...
Date: Tue, 8 Jan 2019 09:16:36 -0500 [thread overview]
Message-ID: <056134a0-469a-749f-caae-62299845a31b@redhat.com> (raw)
In-Reply-To: <37cd6bec-71c2-16f8-48dd-f362b5a71cea@arm.com>
On 1/8/19 8:33 AM, Szabolcs Nagy wrote:
> On 02/01/2019 10:28, Siddhesh Poyarekar wrote:
>> Status of Release blockers:
>>
>> I have reviewed all original release blockers, including a couple of additional ones that got added later but I couldn't get to all of them. As
>> of now, the pending blockers do not look suitable for inclusion at this stage and so will be deferred to 2.30 development.
>
> i'd like to commit some patches that only affect aarch64
> (and only particular uarches there):
>
> memchr and memset for AmpereComputing emag (approved before freeze):
> https://sourceware.org/ml/libc-alpha/2018-12/msg00626.html
> https://sourceware.org/ml/libc-alpha/2018-12/msg00628.html
> https://sourceware.org/ml/libc-alpha/2018-12/msg00820.html
AmpereComputing is not yet listed in the FSF copyright files,
and I don't have confirmation from the FSF (it has been asked).
> ifunc for ares (does not add new implementation):
> https://sourceware.org/ml/libc-alpha/2018-12/msg00754.html
>
> these seem safer to me to commit now than to backport them
> later and should not interfere with the glibc release process.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-01-08 14:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 10:28 glibc 2.29 - Winter is coming Siddhesh Poyarekar
2019-01-02 10:59 ` Florian Weimer
2019-01-02 11:29 ` Siddhesh Poyarekar
2019-01-02 11:52 ` Rafal Luzynski
2019-01-02 18:24 ` Siddhesh Poyarekar
2019-01-03 0:20 ` Rafal Luzynski
2019-01-03 14:32 ` Carlos O'Donell
2019-01-03 20:58 ` Joseph Myers
2019-01-04 21:25 ` Carlos O'Donell
2019-01-07 18:59 ` Florian Weimer
2019-01-02 13:11 ` Gabriel F. T. Gomes
2019-01-02 13:16 ` Florian Weimer
2019-01-02 13:47 ` Siddhesh Poyarekar
2019-01-02 16:02 ` Gabriel F. T. Gomes
2019-01-08 13:33 ` Szabolcs Nagy
2019-01-08 14:16 ` Carlos O'Donell [this message]
2019-01-08 14:21 ` Szabolcs Nagy
2019-01-08 16:50 ` Carlos O'Donell
2019-01-09 10:50 ` Ramana Radhakrishnan
2019-01-09 16:03 ` Carlos O'Donell
[not found] ` <BL0PR01MB4593D75E9376CC15EE8CA24AF7990@BL0PR01MB4593.prod.exchangelabs.com>
2019-01-23 14:07 ` Carlos O'Donell
2019-01-09 5:48 ` Siddhesh Poyarekar
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=056134a0-469a-749f-caae-62299845a31b@redhat.com \
--to=carlos@redhat.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=fxue@os.amperecomputing.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=siddhesh@gotplt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).