From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Kurt Kanzenbach <kurt@linutronix.de>,
Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH v1] futex.2: Document FUTEX_LOCK_PI2
Date: Thu, 29 Jul 2021 12:22:08 +0200 [thread overview]
Message-ID: <0b8992e1-37ae-0b02-a9a6-df635d6fe9b9@gmail.com> (raw)
In-Reply-To: <8735rxjzxm.ffs@tglx>
Hi Kurt, Thomas,
On 7/29/21 10:18 AM, Thomas Gleixner wrote:
> On Fri, Jun 25 2021 at 12:10, Kurt Kanzenbach wrote:
>> FUTEX_LOCK_PI2 is a new futex operation which was recently introduced into the
>> Linux kernel. It works exactly like FUTEX_LOCK_PI. However, it has support for
>> selectable clocks for timeouts. By default CLOCK_MONOTONIC is used. If
>> FUTEX_CLOCK_REALTIME is specified then the timeout is measured against
>> CLOCK_REALTIME.
>>
>> This new operation addresses an inconsistency in the futex interface:
>> FUTEX_LOCK_PI only works with timeouts based on CLOCK_REALTIME in contrast to
>> all the other PI operations.
>>
>> Document the FUTEX_LOCK_PI2 command.
>>
>> Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de>
Sorry, I merged it and forgot to reply. Patch applied (And a minor
inconsistency fixed: s/5.14.0/5.14/ ; All references to kernel 5
versions have 2 fields in the manual pages). And some other minor fixes
too.
>
> Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
>
Thanks for the review. I'll add that line.
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-07-29 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 10:10 [PATCH v1] futex.2: Document FUTEX_LOCK_PI2 Kurt Kanzenbach
2021-07-29 8:18 ` Thomas Gleixner
2021-07-29 10:22 ` Alejandro Colomar (man-pages) [this message]
2021-07-29 10:58 ` Kurt Kanzenbach
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=0b8992e1-37ae-0b02-a9a6-df635d6fe9b9@gmail.com \
--to=alx.manpages@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=kurt@linutronix.de \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.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).