public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2023-05-29)
Date: Mon, 29 May 2023 09:59:41 -0400	[thread overview]
Message-ID: <03a145f6-4b0a-892a-8574-e0b73d4cf2e9@redhat.com> (raw)

Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update

Meeting: 2023-05-29 @ 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 275.
 * Carlos' SLI at 176 days average and 50345 total patch days.
 * Carlos: I need to switch to doing more patch review, but I'm making progress on pthread cond var lost signal.
 * Start review at 70196. Previous start at 69335. 53 patches?
 * [v2] fcntl fortification (Sergey)
  * Adhemerla: Plan to reivew.
  * Siddhesh: Likewise.
 * Fix misspellings in elf/ -- BZ 25337 (Paul)
  * Carlos: Will review ASAP. Consensus is Paul can commit.
 * [v10,1/3] x86: Increase `non_temporal_threshold` to roughly `sizeof_L3 / 4` (Noah)
  * DJ reviewed v9, should review v10.
  * Carlos has to reivew downstream STREAMS benchmark data.
 * [v2] ifaddrs: Get rid of alloca (Joe)
  * Adhemerval: Reviewed last one, Will review this one.
 * [v2] io: Fix record locking contants on 32 bit arch with 64 bit default time_t (BZ#30477) (Adhemerval)
  * Carlos: I'll review this.
  * Adhemerval: Reviewed the existing code to see if there any other cases of this (requested by Florian).
  * https://sourceware.org/pipermail/libc-alpha/2023-May/148502.html
 * posix: Add error message for EAI_OVERFLOW (Dridi)
  * https://pubs.opengroup.org/onlinepubs/9699919799/functions/gai_strerror.html
  * Should have strings for all error messages. Is this the only missing one?
  * Asked Arjun for review.
 * LoongArch: Fix inconsistency in SHMLBA macro values between glibc and kernel (Caiyin Yu)
  * Needs review. Not easy to make a test for this (Florian's suggestion)
 * [v7] nptl: Fix Race conditions in pthread cancellation [BZ#12683] (Adhemerval)
  * Adhemerval: Moved to a single file.
  * Carlos: Will review today.
 * [v5] Add pidfd_spawn, pidfd_spawnp, pidfd_fork, and pidfd_getpid (Adhemerval)
  * Needs review.
 * posix: fix fnmatch() inconsistency BZ#30483 (Carlo Arenas)
  * Adhemerval: Please add test case? Changes requested.
 * Stopped at 69810.
 * Add clone3 support for multiple architectures (Adhemerval)
  * Needs arch review.
  * Palmer will try to look at RISC-V rv64 clone3 internal impl.
 * Restarting at 69810
 * [v3] vfprintf-internal: Get rid of alloca. (Joe)
 * [v2] elf: Make more functions available for binding during dlclose (bug 30425) (Florian)
  * Carlos: Changes requested. Will follow up with Florian.
 * [v2] libio: Add nonnull attribute for most FILE * arguments in stdio.h (Xi)
  * Carlos: Needs DCO or assignment.
 * Stopped at 69621.

-- 
Cheers,
Carlos.


                 reply	other threads:[~2023-05-29 13:59 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=03a145f6-4b0a-892a-8574-e0b73d4cf2e9@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).