From: Ingo Molnar <mingo@kernel.org>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: Jonathan Corbet <corbet@lwn.net>, Ingo Molnar <mingo@elte.hu>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH 1/1] Documentation/robust-futex-API: remove alternative language
Date: Wed, 18 Feb 2015 18:38:51 +0100 [thread overview]
Message-ID: <20150218173851.GA31566@gmail.com> (raw)
In-Reply-To: <1424098577-5492-1-git-send-email-xypron.glpk@gmx.de>
* Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> The man-pages as well as robust-futexes.txt use the word
> "contend" for a situation where two threads try to access
> the same futex at the same time.
>
> To avoid confusion robust-futex-API.txt should not use
> "contest" as alternative language.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> Documentation/robust-futex-ABI.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/robust-futex-ABI.txt b/Documentation/robust-futex-ABI.txt
> index 16eb314..e6a5532 100644
> --- a/Documentation/robust-futex-ABI.txt
> +++ b/Documentation/robust-futex-ABI.txt
> @@ -18,8 +18,8 @@ required for futexes is:
> by the exiting thread.
>
> The existing normal futexes already provide a "Fast Userspace Locking"
> -mechanism, which handles uncontested locking without needing a system
> -call, and handles contested locking by maintaining a list of waiting
> +mechanism, which handles uncontended locking without needing a system
> +call, and handles contended locking by maintaining a list of waiting
So this was a typo, not alternative language! :-)
Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
prev parent reply other threads:[~2015-02-18 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 14:56 [PATCH 1/1] Documentation/robust-futex-API: remove alternative language Heinrich Schuchardt
2015-02-16 17:13 ` Jonathan Corbet
2015-02-18 17:38 ` Ingo Molnar [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=20150218173851.GA31566@gmail.com \
--to=mingo@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtk.manpages@gmail.com \
--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