From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/3] futex.2: tfix
Date: Wed, 30 Dec 2015 20:36:04 +0100 [thread overview]
Message-ID: <56843224.3010708@gmail.com> (raw)
In-Reply-To: <1451485000-350-1-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
On 12/30/2015 03:16 PM, Jakub Wilk wrote:
> ---
> man2/futex.2 | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Thanks, Jakub. Applied.
Cheers,
Michael
> diff --git a/man2/futex.2 b/man2/futex.2
> index 7144bf1..8c6c023 100644
> --- a/man2/futex.2
> +++ b/man2/futex.2
> @@ -88,7 +88,7 @@ on the same futex word.
> .\" Totally ordered with respect futex operations refers to semantics
> .\" of the ACQUIRE/RELEASE operations and how they impact ordering of
> .\" memory reads and writes. The kernel futex operations are protected
> -.\" by spinlocks, which ensure that that all operations are serialized
> +.\" by spinlocks, which ensure that all operations are serialized
> .\" with respect to one another.
> .\"
> .\" This is a lot to attempt to define in this document. Perhaps a
> @@ -125,11 +125,11 @@ wait operation.
> This
> .BR futex ()
> operation will block if and only if the lock is still acquired
> -(i.e., the value in the futex word still matches the "acquiired state").
> +(i.e., the value in the futex word still matches the "acquired state").
> 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 a futex word
> -(this can be be further optimized to avoid unnecessary wake-ups).
> +(this can be further optimized to avoid unnecessary wake-ups).
> See
> .BR futex (7)
> for more detail on how to use futexes.
>
--
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-12-30 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 14:16 [PATCH 1/3] futex.2: tfix Jakub Wilk
[not found] ` <1451485000-350-1-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2015-12-30 14:16 ` [PATCH 2/3] fcntl.2: tfix Jakub Wilk
[not found] ` <1451485000-350-2-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2015-12-30 19:36 ` Michael Kerrisk (man-pages)
2015-12-30 14:16 ` [PATCH 3/3] Changes.old: tfix Jakub Wilk
[not found] ` <1451485000-350-3-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2015-12-30 19:36 ` Michael Kerrisk (man-pages)
2015-12-30 19:36 ` 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=56843224.3010708@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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 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 NNTP newsgroup(s).