linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 2/2] futex.2: tfix
Date: Mon,  4 Jan 2016 16:59:35 +0100	[thread overview]
Message-ID: <1451923175-4316-2-git-send-email-jwilk@jwilk.net> (raw)
In-Reply-To: <1451923175-4316-1-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>

Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>

diff --git a/man2/futex.2 b/man2/futex.2
index 8c6c023..7cf0d0b 100644
--- a/man2/futex.2
+++ b/man2/futex.2
@@ -516,7 +516,7 @@ unlock(A);
 If a waker thread used
 .BR FUTEX_WAKE ,
 then all waiters waiting on B would be woken up,
-and they would would all try to acquire lock A.
+and they would all try to acquire lock A.
 However, waking all of the threads in this manner would be pointless because
 all except one of the threads would immediately block on lock A again.
 By contrast, a requeue operation wakes just one waiter and moves
-- 
2.6.4

--
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

  parent reply	other threads:[~2016-01-04 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 15:59 [PATCH 1/2] ptrace.2: tfix Jakub Wilk
     [not found] ` <1451923175-4316-1-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2016-01-04 15:59   ` Jakub Wilk [this message]
     [not found]     ` <1451923175-4316-2-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2016-01-08 16:26       ` [PATCH 2/2] futex.2: tfix Michael Kerrisk (man-pages)
2016-01-08 16:26   ` [PATCH 1/2] ptrace.2: tfix 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=1451923175-4316-2-git-send-email-jwilk@jwilk.net \
    --to=jwilk-txgolizoknreowh0uzbu5w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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).