From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/1] futex.2: tfix
Date: Sat, 18 Apr 2015 20:43:34 +0200 [thread overview]
Message-ID: <5532A5D6.8030304@gmail.com> (raw)
In-Reply-To: <1428947385-32126-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
On 04/13/2015 07:49 PM, Heinrich Schuchardt wrote:
> Signed-off-by: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
Thanks, Heinrich. 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 9bfd934..baf356d 100644
> --- a/man2/futex.2
> +++ b/man2/futex.2
> @@ -93,7 +93,7 @@ The call to
> will block if and only if the lock is still acquired.
> When releasing the lock, a thread has to first reset the
> lock state to not acquired and then execute a futex
> -operation that wakes threads blocked on the lock flag used as futex word.
> +operation that wakes threads blocked on the lock flag used as futex word
> (this can be be further optimized to avoid unnecessary wake-ups).
> See
> .BR futex (7)
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-04-18 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 17:49 [PATCH 1/1] futex.2: tfix Heinrich Schuchardt
[not found] ` <1428947385-32126-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2015-04-18 18:43 ` Michael Kerrisk (man-pages) [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=5532A5D6.8030304@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=xypron.glpk-Mmb7MZpHnFY@public.gmane.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 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.