From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>,
DJ Delorie <dj@redhat.com>,
Simon Chopin <simon.chopin@canonical.com>
Subject: Monday Patch Queue Review update (2024-03-04)
Date: Mon, 4 Mar 2024 10:01:01 -0500 [thread overview]
Message-ID: <62e1d5f8-9384-4310-8da2-664f9b8af974@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2024-03-04 @ 0900h EST5EDT
Video/Audio: https://bbb.linuxfoundation.org/room/adm-alk-1uu-7fu
IRC: #glibc on OFTC.
Review new patches and restart review at the top.
* State NEW delegate NOBODY at 420 patches.
* Start at 86657.
* codonell: Noted Red Hat CI is down, and pinged DJ.
* maxim: Noted Linaro CI will follow once it's up again.
* v2: Improve wcsstr (Adhemerval)
* Re-assigned to DJ.
* Extending TLS testing and fixing TLS gnu2 for ARM (Adhemerval)
* Reviewed pool: Arjun
* Discussed the state of TLS ABI and descriptors.
* HJ: Should we raise this to other machine maintainers?
* Adhemerval: I have an action item to raise this with Loongarch.
* optimize memmem for short needles (James Tirta Halim)
* Maxim to review.
* [v2] LoongArch: Add support for TLS Descriptors (Meng)
* Adhemerval to review.
* System-wide tunables (DJ)
* Failed CI for 32-bit targets.
* Adhemerval to review.
* Extend rseq support (Michael)
* codonell: I'll follow up with DJ to discuss if this should get pushed or if any remaining blockers exists.
* locale: Handle loading a missing locale twice (Bug 14247) (Carlos)
* Adhemerval: Requested v2 with minor changes.
* Update RISC-V relocations (Andreas)
* Reviewer pool: Carlos to review.
* [v3] Always define __USE_TIME_BITS64 when 64 bit time_t is used (Adhemerval)
* Reviewer pool: DJ
* codonell: I'll talk to Siddhesh about running the cleanup script.
* New TLS usage in libgcc_s.so.1, compatibility impact (Florian)
* Carlos to review.
* Don't check signatures in build-many-glibcs.py (Palmer)
* Reviewer pool: Simon Chopin
* Stopped at 83697.
* Adhemerval: We've had some issues with the RISC-V commits that broke things.
* codonell: We need to reply on list that it was broken. Would this be resolved with pre-commit CI?
* Discussed SPDX, and the Licenses file and making some progress to simplify this for downstream distributions.
--
Cheers,
Carlos.
next reply other threads:[~2024-03-04 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 15:01 Carlos O'Donell [this message]
2024-03-04 18:54 ` DJ Delorie
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=62e1d5f8-9384-4310-8da2-664f9b8af974@redhat.com \
--to=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=simon.chopin@canonical.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).