From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Valentin Rothberg <valentinrothberg@gmail.com>
Cc: corbet@lwn.net, josh@joshtriplett.org,
linux-kernel@vger.kernel.org, dave@stgolabs.net
Subject: Re: [PATCH] Documentation: locktorture.txt: corret MUTEXES typo
Date: Wed, 7 Oct 2015 08:42:01 -0700 [thread overview]
Message-ID: <20151007154201.GK3910@linux.vnet.ibm.com> (raw)
In-Reply-To: <1444216507-17380-1-git-send-email-valentinrothberg@gmail.com>
On Wed, Oct 07, 2015 at 01:15:07PM +0200, Valentin Rothberg wrote:
> s/CONFIG_RT_MUTEX/CONFIG_RT_MUTEXES/
>
> Signed-off-by: Valentin Rothberg <valentinrothberg@gmail.com>
Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Also copying Davidlohr for his take.
> ---
> I detected the typo with scripts/checkkconfigsymbols.py
>
> Documentation/locking/locktorture.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/locking/locktorture.txt b/Documentation/locking/locktorture.txt
> index a2ef3a929bf1..66b70df5c5ec 100644
> --- a/Documentation/locking/locktorture.txt
> +++ b/Documentation/locking/locktorture.txt
> @@ -53,7 +53,7 @@ torture_type Type of lock to torture. By default, only spinlocks will
> o "mutex_lock": mutex_lock() and mutex_unlock() pairs.
>
> o "rtmutex_lock": rtmutex_lock() and rtmutex_unlock()
> - pairs. Kernel must have CONFIG_RT_MUTEX=y.
> + pairs. Kernel must have CONFIG_RT_MUTEXES=y.
>
> o "rwsem_lock": read/write down() and up() semaphore pairs.
>
> --
> 2.6.1
>
next prev parent reply other threads:[~2015-10-07 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 11:15 [PATCH] Documentation: locktorture.txt: corret MUTEXES typo Valentin Rothberg
2015-10-07 15:42 ` Paul E. McKenney [this message]
2015-10-07 16:29 ` Davidlohr Bueso
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=20151007154201.GK3910@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=corbet@lwn.net \
--cc=dave@stgolabs.net \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=valentinrothberg@gmail.com \
/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.