From: Yu-Chien Peter Lin <peterlin@andestech.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: <libc-alpha@sourceware.org>, <fweimer@redhat.com>,
<ycliang@andestech.com>, <alankao@andestech.com>
Subject: Re: [PATCH] nptl: Fix typo in error message
Date: Fri, 30 Sep 2022 14:28:46 +0000 [thread overview]
Message-ID: <Yzb9HtzvGcz0sIiW@APC323> (raw)
In-Reply-To: <87o7uy7b3x.fsf@mid.deneb.enyo.de>
On Thu, Sep 29, 2022 at 12:01:38PM +0200, Florian Weimer wrote:
> * Yu Chien Peter Lin:
>
> > Signed-off-by: Yu Chien Peter Lin <peterlin@andestech.com>
> > ---
> > nptl/tst-setuid2.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/nptl/tst-setuid2.c b/nptl/tst-setuid2.c
> > index aff3b1a97d..fed2671b01 100644
> > --- a/nptl/tst-setuid2.c
> > +++ b/nptl/tst-setuid2.c
> > @@ -77,7 +77,7 @@ run_on_thread (void (*func) (void))
> >
> > ret = pthread_cond_signal (&cond_send);
> > if (ret != 0)
> > - FAIL ("pthread_mutex_lock (%s): %d", __func__, ret);
> > + FAIL ("pthread_cond_signal (send): %d", ret);
> >
> > ret = pthread_mutex_lock (&mutex);
> > if (ret != 0)
> > @@ -87,7 +87,7 @@ run_on_thread (void (*func) (void))
> > {
> > ret = pthread_cond_wait (&cond_recv, &mutex);
> > if (ret != 0)
> > - FAIL ("pthread_mutex_wait (%s): %d", __func__, ret);
> > + FAIL ("pthread_cond_wait (recv): %d", ret);
> > }
> > ret = pthread_mutex_unlock (&mutex);
> > if (ret != 0)
>
> Maybe introduce xpthread_cond_signal in a separate patch and use
> xpthread_cond_signal and xpthread_cond_wait instead? The latter
> already exists.
Hi, Florian
I would introduce xpthread_cond_signal with a new patch, and also use
test-driver.c, thanks for your suggestion.
Best regards,
Peter Lin
prev parent reply other threads:[~2022-09-30 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 8:57 Yu Chien Peter Lin
2022-09-29 10:01 ` Florian Weimer
2022-09-30 14:28 ` Yu-Chien Peter Lin [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=Yzb9HtzvGcz0sIiW@APC323 \
--to=peterlin@andestech.com \
--cc=alankao@andestech.com \
--cc=fw@deneb.enyo.de \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=ycliang@andestech.com \
/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).