From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2021-11-08)
Date: Wed, 10 Nov 2021 11:37:34 -0500 [thread overview]
Message-ID: <708efa6c-0092-cfe5-5dd5-2a1f6262f5ad@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2021-11-01 @ 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, 289 patches.
* 47212: io: Refactor close_range and closefrom
* Adhemerval: Pointed out a discrepancy for patch review and refactoring.
* 47211: powerpc: Define USE_PPC64_NOTOC iff compiler and linker also supports it
* Adhemerval: These are further fixes for lld. Discussing with IBM.
* Discussed the current gABI issues that relate to ensuring that old ld.so
can safely fail when new binaries are run on old system.
* Waiting for Cary Coutant to publish the gABI repo.
* Series 4535: Update Makefile fragments for DSO sorting tests
* Florain: Needs changes. Post v2.
* 47161: Remove the unnecessary +make-deps
* Needs review.
* 47065: powerpc: Use FLAG_ELF_LIBC6 for 32-bit known libraries
* Needs review from Florian or Tulio.
* 47064: Fix memmove call in vfprintf-internal.c:group_number
* Florian: Given that I produced the bug I should review it.
* 47061: [v3] x86: Optimize atomic_compare_and_exchange_[val|bool]_acq [BZ #28537]
* Needs review.
* Carlos: As x86 maintainer you could just wait and push. There is a lot of internal CPU details that this depends upon.
* Carlos: We need a comment here to expalin the redundant read.
* 47048: [v2] elf: Use the minimal malloc on tunables_strdup
* Siddhesh should review.
* https://sourceware.org/pipermail/libc-alpha/2021-November/132688.html
* Florian needs review.
* Adhemerval: 64-bit time_t recvmsg review.
* Florian: Assign that to me for review.
* Florian: May you please repost your LD_AUDIT patches? (to Adhemerval)
--
Cheers,
Carlos.
reply other threads:[~2021-11-10 16:37 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=708efa6c-0092-cfe5-5dd5-2a1f6262f5ad@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).