From: "Malte Skarupke" <malteskarupke@fastmail.fm>
To: "Sam James" <sam@gentoo.org>, "Carlos O'Donell" <carlos@redhat.com>
Cc: Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 0/9] Patch to fix glibc condition variable bug (BZ 25847)
Date: Sat, 18 Mar 2023 08:08:38 -0400 [thread overview]
Message-ID: <b4f46b70-e89e-46e6-9e82-ed5145f7a48b@app.fastmail.com> (raw)
In-Reply-To: <EE4A57AB-517A-49A7-B781-9FFB6C90C668@gentoo.org>
Hi again, is there any update on this? I can also hop on a call or chat with someone if that helps with the review.
Let me know,
Malte
--
Malte Skarupke
malteskarupke@fastmail.fm
Am Di, 7. Feb 2023, um 21:51, schrieb Sam James:
>> On 8 Feb 2023, at 02:48, Malte Skarupke via Libc-alpha <libc-alpha@sourceware.org> wrote:
>>
>> Ping. I really think you want these changes. These are patches that fix the issue with no downsides. The code is clearer, performance better, and a really bad bug is fixed.
>>
>
> It's been a few days and your patch was noted in Monday's patch review.
> It looks like it's on Carlos' list to review
> shortly.
>
>> --
>> Malte Skarupke
>> malteskarupke@fastmail.fm
>
> Dateianhänge:
> * signature.asc
prev parent reply other threads:[~2023-03-18 12:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 2:18 malteskarupke
2023-01-28 2:18 ` [PATCH 1/9] pthreads NPTL: lost wakeup fix 2 malteskarupke
2023-01-28 2:18 ` [PATCH 2/9] nptl: Update comments and indentation for new condvar implementation malteskarupke
2023-01-28 2:18 ` [PATCH 3/9] nptl: Remove unnecessary catch-all-wake in condvar group switch malteskarupke
2023-01-28 2:18 ` [PATCH 4/9] nptl: Remove unnecessary quadruple check in pthread_cond_wait malteskarupke
2023-01-28 2:18 ` [PATCH 5/9] nptl: Remove g_refs from condition variables malteskarupke
2023-01-28 2:18 ` [PATCH 6/9] nptl: Use a single loop in pthread_cond_wait instaed of a nested loop malteskarupke
2023-01-28 2:18 ` [PATCH 7/9] nptl: Fix indentation malteskarupke
2023-01-28 2:18 ` [PATCH 8/9] nptl: rename __condvar_quiesce_and_switch_g1 malteskarupke
2023-01-28 2:18 ` [PATCH 9/9] nptl: Use all of g1_start and g_signals malteskarupke
2023-02-08 2:48 ` [PATCH 0/9] Patch to fix glibc condition variable bug (BZ 25847) Malte Skarupke
2023-02-08 2:51 ` Sam James
2023-03-18 12:08 ` Malte Skarupke [this message]
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=b4f46b70-e89e-46e6-9e82-ed5145f7a48b@app.fastmail.com \
--to=malteskarupke@fastmail.fm \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=sam@gentoo.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).