From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2022-03-28)
Date: Tue, 29 Mar 2022 16:49:13 -0400 [thread overview]
Message-ID: <86ceb4f5-bf31-9fb1-bff4-fdaaa2ab6da8@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2022-03-28 @ 0900h EST5EDT
Video/Audio: https://bluejeans.com/9093064454
IRC: #glibc on OFTC.
Review new patches and restart review at the top.
* State NEW, delegate NOBODY is 312 patches.
* Adhemerval tries to push.
"Enumerating objects: 1581, done.
Counting objects: 100% (1581/1581), done.
Delta compression using up to 24 threads
Compressing objects: 100% (807/807), done.
Writing objects: 100% (1093/1093), 162.32 KiB | 13.53 MiB/s, done.
Total 1093 (delta 950), reused 298 (delta 272), pack-reused 0
remote: Resolving deltas: 100% (950/950), completed with 415 local objects.
remote: *** This update introduces too many new commits (121), which would
remote: *** trigger as many emails, exceeding the current limit (100).
remote: *** Contact your repository adminstrator if you really meant
remote: *** to generate this many commit emails.
remote: error: hook declined to update refs/heads/azanella/clang"
* Carlos reviewed and it's max-commit-emails, which can be set to 1000 to avoid
this problem and allow you to publish a branch for review.
* [v2] nptl: Add backoff mechanism to spinlock loop (Wangyang Guo)
* We can't use random-bits.h (30 cycles)
* Can we use tid?
* Can we use rdtsc? (18 cycles)
* At least one microbench should be contributed.
* [v1,1/2] x86: Small improvements for wcscpy-ssse3 (Noah)
* Waiting for feedback from Zhaoxin cpu discussion, see:
https://sourceware.org/pipermail/libc-alpha/2022-March/137354.html
* [v2,1/6] x86: Remove {w}memcmp-ssse3 (Noah)
* HJ reviewing.
* rwlock for async application
* This is an RFC for glibc to deviate from POSIX behaviour.
* Add HWCAP2_AFP, HWCAP2_RPRES from Linux 5.17 to AArch64 bits/hwcap.h (Joseph)
* Accepted by Szabolcs [Arm]
* Note from Adhemvarl that POSIX will add strlcpy and strlcat
* Prposed by Florian in 2016.
* https://www.austingroupbugs.net/view.php?id=986
* https://sourceware.org/glibc/wiki/strlcpy
* Stopped at 52304.
* realpath: Bring back GNU extension on ENOENT and EACCES [BZ #28996]
* Adhemerval will review.
* [v5] Allow for unpriviledged nested containers
* Adhemerval asking if we are going to accept this patch?
* Carlos to review this to completion to unblock Adhemerval.
* This blocks the syslog https://patchwork.sourceware.org/project/glibc/list/?series=8031
* Siddhesh notes that DNS tests no longer depend on proc mount.
* However we still have tests that use DNS and can fail.
* They need to be ported to use the in-process test DNS resolver or changed.
* Support DT_RELR relative relocation format review.
* What is the status of DT_RELR for AArch64? Currently unimplemented.
* Looking for review of v6 patches.
* No technical blockers. Push April 11th if no further reviews.
--
Cheers,
Carlos.
next reply other threads:[~2022-03-29 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 20:49 Carlos O'Donell [this message]
2022-03-29 22:22 ` Fangrui Song
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=86ceb4f5-bf31-9fb1-bff4-fdaaa2ab6da8@redhat.com \
--to=carlos@redhat.com \
--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).