From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>,
Thomas Gleixner <tglx@linutronix.de>,
Darren Hart <dvhart@infradead.org>,
Torvald Riegel <triegel@redhat.com>
Cc: mtk.manpages@gmail.com, "Carlos O'Donell" <carlos@redhat.com>,
Ingo Molnar <mingo@elte.hu>, Jakub Jelinek <jakub@redhat.com>,
linux-man <linux-man@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Arnd Bergmann <arnd@arndb.de>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Linux API <linux-api@vger.kernel.org>,
Roland McGrath <roland@hack.frob.com>,
Anton Blanchard <anton@samba.org>,
Eric Dumazet <edumazet@google.com>,
bill o gallmeister <bgallmeister@gmail.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Daniel Wagner <wagi@monom.org>, Rich Felker <dalias@libc.org>,
Andy Lutomirski <luto@amacapital.net>,
bert hubert <bert.hubert@netherlabs.nl>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: Next round: revised futex(2) man page for review
Date: Mon, 27 Jul 2015 16:44:16 +0200 [thread overview]
Message-ID: <55B643C0.1080807@gmail.com> (raw)
In-Reply-To: <trinity-f9a7a25f-09e9-4409-b656-0e035dfca0b5-1438006633780@msvc-mesg-gmx010>
On 07/27/2015 04:17 PM, Heinrich Schuchardt wrote:
> instruction. A thread maybe unable
>
> to << missing word
>
> acquire a lock because it is
> already acquired by another thread. It then may pass the lock's
> flag as futex word and the value representing the acquired state
> as the expected value to a futex() wait operation.
Thanks, Heinrich. Fixed.
Cheers,
Michael
next parent reply other threads:[~2015-07-27 14:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <trinity-f9a7a25f-09e9-4409-b656-0e035dfca0b5-1438006633780@msvc-mesg-gmx010>
2015-07-27 14:44 ` Michael Kerrisk (man-pages) [this message]
2015-07-27 12:07 Next round: revised futex(2) man page for review Michael Kerrisk (man-pages)
2015-07-28 20:23 ` Thomas Gleixner
2015-07-28 20:45 ` Peter Zijlstra
2015-07-28 21:03 ` Thomas Gleixner
2015-08-08 6:56 ` Michael Kerrisk (man-pages)
2015-07-29 2:09 ` Davidlohr Bueso
2015-07-29 4:11 ` Darren Hart
2015-07-29 4:21 ` Darren Hart
2015-07-29 12:00 ` Thomas Gleixner
2015-07-30 8:19 ` Michael Kerrisk (man-pages)
2015-08-08 6:53 ` Michael Kerrisk (man-pages)
2015-08-19 23:17 ` Thomas Gleixner
2015-08-26 6:29 ` Darren Hart
2015-10-07 8:30 ` Michael Kerrisk (man-pages)
2015-10-08 14:36 ` Darren Hart
2015-08-05 22:21 ` Darren Hart
2015-08-08 6:57 ` Michael Kerrisk (man-pages)
2015-08-24 21:47 ` Darren Hart
2015-08-19 22:40 ` Thomas Gleixner
2015-08-18 12:45 ` Darren Hart
2015-10-07 9:34 ` Michael Kerrisk (man-pages)
2015-10-08 14:46 ` Darren Hart
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=55B643C0.1080807@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=anton@samba.org \
--cc=arnd@arndb.de \
--cc=bert.hubert@netherlabs.nl \
--cc=bgallmeister@gmail.com \
--cc=carlos@redhat.com \
--cc=dalias@libc.org \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=edumazet@google.com \
--cc=jakub@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=roland@hack.frob.com \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=triegel@redhat.com \
--cc=wagi@monom.org \
--cc=xypron.glpk@gmx.de \
/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).