From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2024-04-08)
Date: Mon, 8 Apr 2024 10:33:18 -0300 [thread overview]
Message-ID: <0477a534-fc01-4220-83e3-e5f76f89dc24@linaro.org> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2024-04-08 @ 0900h EST5EDT
Video/Audio: https://bbb.linuxfoundation.org/room/adm-alk-1uu-7fu
IRC: #glibc on OFTC.
Review new patches and attendee requested reviews.
State NEW delegate NOBODY at 374 patches.
* 88171: [v2] login: Use unsigned 32-bit types for seconds-since-epoch
* Have a patch that distro maintainers can pick to get around it the y2038 issues with utmp/utmpx/lastlogin.
* 88164: Enhanced CPU diagnostics for ld.so
* Nsz raised some concerns about code and printing information for aarch64.
* Delegate azanella
* 88160: libsupport: Add xgetpeername
* Assigned to arjun
* 88147: [RFC] Enable libmvec support for RISC-V
* Let RISC-V maintainers to handle it.
* 88122: Use crtbeginT.o and crtend.o for non-PIE static executables
* Assigned to codonell
* 87989: arc4random: fix getrandom fallback to /dev/urandom
* Changes requested
* 87981: elf: Don't call fatal_error in _dl_signal_error
* Florian will try to come up with a testcase to trigger the deleted code path.
* Florian
* Nothing to add.
* Szabolcs
* Nothing to add.
* H.J
* Nothing to add.
* Maxim
* Nothing to add.
reply other threads:[~2024-04-08 13:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0477a534-fc01-4220-83e3-e5f76f89dc24@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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).