[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a48ce53c-5510-b779-c42d-b2e7367a442e@redhat.com>
Date: Mon, 30 Jan 2023 11:19:40 -0500
From: Waiman Long <longman@...hat.com>
To: Antonio Paolillo <antonio.paolillo@...wei.com>,
peterz@...radead.org, mingo@...hat.com, will@...nel.org,
boqun.feng@...il.com, corbet@....net
Cc: linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH] doc: locktorture fix
On 1/30/23 07:55, Antonio Paolillo wrote:
> The actual build option for rtmutex lock is `CONFIG_RT_MUTEXES`, not
> `CONFIG_RT_MUTEX`.
>
> Signed-off-by: Antonio Paolillo <antonio.paolillo@...wei.com>
> ---
> Documentation/locking/locktorture.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/locking/locktorture.rst b/Documentation/locking/locktorture.rst
> index dfaf9fc883f4..3f7b44e2c070 100644
> --- a/Documentation/locking/locktorture.rst
> +++ b/Documentation/locking/locktorture.rst
> @@ -67,7 +67,7 @@ torture_type
>
> - "rtmutex_lock":
> rtmutex_lock() and rtmutex_unlock() pairs.
> - Kernel must have CONFIG_RT_MUTEX=y.
> + Kernel must have CONFIG_RT_MUTEXES=y.
>
> - "rwsem_lock":
> read/write down() and up() semaphore pairs.
Acked-by: Waiman Long <longman@...hat.com>
Powered by blists - more mailing lists