From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Jing Peng <pj.hades@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] futex.2: tfix
Date: Sat, 21 Nov 2020 22:25:54 +0100 [thread overview]
Message-ID: <afa70208-e919-644c-2dfc-cda9946187a6@gmail.com> (raw)
In-Reply-To: <CAL+Ps4T=fhfb-tBKKBz5vUXPVKB6nWM+E32dxyTMMBzZqXZByw@mail.gmail.com>
On 11/21/20 10:08 PM, Jing Peng wrote:
> In the comment of the example program, the peer blocks on fwait()
> rather than fpost().
>
> Signed-off-by: Jing Peng <pj.hades@gmail.com>
Thanks, Jing Peng! Patch applied.
Cheers,
Michael
> ---
> man2/futex.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/futex.2 b/man2/futex.2
> index 76c89f16c..5e006784f 100644
> --- a/man2/futex.2
> +++ b/man2/futex.2
> @@ -1809,7 +1809,7 @@ fwait(uint32_t *futexp)
>
> /* Release the futex pointed to by \(aqfutexp\(aq: if the futex currently
> has the value 0, set its value to 1 and the wake any futex waiters,
> - so that if the peer is blocked in fpost(), it can proceed. */
> + so that if the peer is blocked in fwait(), it can proceed. */
>
> static void
> fpost(uint32_t *futexp)
> --
> 2.29.1
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-11-21 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 21:08 [PATCH] futex.2: tfix Jing Peng
2020-11-21 21:25 ` Michael Kerrisk (man-pages) [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-03 14:08 [patch] " Davide Benini
2022-03-06 17:39 ` Alejandro Colomar (man-pages)
2021-02-20 20:12 [PATCH] " edef
2021-02-20 21:47 ` Michael Kerrisk (man-pages)
2015-03-29 18:23 Heinrich Schuchardt
[not found] ` <1427653404-26501-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2015-04-11 6:55 ` Michael Kerrisk (man-pages)
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=afa70208-e919-644c-2dfc-cda9946187a6@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=pj.hades@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.