From: Waiman Long <waiman.long@hpe.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jonathan Corbet <corbet@lwn.net>, <linux-kernel@vger.kernel.org>,
<linux-doc@vger.kernel.org>, Davidlohr Bueso <dave@stgolabs.net>,
Scott J Norton <scott.norton@hpe.com>,
Douglas Hatch <doug.hatch@hpe.com>
Subject: Re: [RFC PATCH 4/4] futex, doc: TO futexes document
Date: Thu, 22 Sep 2016 09:06:01 -0400 [thread overview]
Message-ID: <57E3D739.60205@hpe.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1609221239150.5599@nanos>
On 09/22/2016 06:40 AM, Thomas Gleixner wrote:
> On Tue, 6 Sep 2016, Waiman Long wrote:
>> This patch adds a new document file on how to use the TO futexes.
> Documentation is nice, but the proper place for documenting this is the
> futex(2) man page.
>
> Thanks,
>
> tglx
Yes, I will certainly send patch to update the manpages after the new
futex gets merged into the upstream kernel. Or should I do that in parallel?
Cheers,
Longman
next prev parent reply other threads:[~2016-09-22 13:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 18:53 [RFC PATCH 0/4] futex: Introducing throughput-optimized futexes Waiman Long
2016-09-06 18:53 ` [RFC PATCH 1/4] futex: Add futex_set_timer() helper function Waiman Long
2016-09-06 18:53 ` [RFC PATCH 2/4] futex: Rename futex_pi_state to futex_state Waiman Long
2016-09-06 18:53 ` [RFC PATCH 3/4] futex: Throughput-optimized (TO) futexes Waiman Long
2016-09-22 13:32 ` Thomas Gleixner
2016-09-23 2:44 ` Waiman Long
2016-09-23 10:16 ` Thomas Gleixner
2016-09-06 18:53 ` [RFC PATCH 4/4] futex, doc: TO futexes document Waiman Long
2016-09-22 10:40 ` Thomas Gleixner
2016-09-22 13:06 ` Waiman Long [this message]
2016-09-22 13:51 ` Thomas Gleixner
2016-09-22 19:14 ` Waiman Long
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=57E3D739.60205@hpe.com \
--to=waiman.long@hpe.com \
--cc=corbet@lwn.net \
--cc=dave@stgolabs.net \
--cc=doug.hatch@hpe.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=scott.norton@hpe.com \
--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 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.