From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2023-03-20)
Date: Mon, 20 Mar 2023 09:46:59 -0400 [thread overview]
Message-ID: <de205c38-fab4-875f-8082-756966d234e9@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2023-03-20 @ 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 285 patches.
* Carlos' SLI at 128 days.
* Starting review at 66620.
* Marked the 64-bit GNU Hurd port ad RFC.
* implement dlmem() function (stsp)
* Carlos to review given previous comments.
* posix: Fix some null deferences in wordexp [BZ #18096]
* Andreas requested changes.
* htl: move some symbol into libc (Guy-Fleury Iteriteka)
* [v2] aligned_alloc: conform to C17 (DJ)
* Carlos can review. However, v3 required, no new symbol should be exported.
* Improve fmod and fmodf (Adhemerval)
* v3 needs udpated tests.
* C2x strtol binary constant handling: Fix special case "0b" (Bruno)
* Early testing. Needs test case.
* getlogin_r: fix missing fallback if loginid is unset (bug 30235)
* Needs more review than just the name.
* [v2] x86: Set FSGSBASE to active if enabled by kernel
* Florian to review today.
* Stop at 66328.
* Cupertino raised the "Created tunable to force small pages on stack allocation." patch.
* Repost v2.
* Remove --with-default-link option (Adhemerval)
* Carlos to review last 2 patches.
* Patch to fix glibc condition variable bug (BZ 25847)
* Discussed status of review. No blockers, still reviewing results.
--
Cheers,
Carlos.
reply other threads:[~2023-03-20 13:47 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=de205c38-fab4-875f-8082-756966d234e9@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).