* [PATCH] docs: locking: refer to the actual existing config names
@ 2023-02-20 16:57 Lukas Bulwahn
2023-02-20 17:18 ` Waiman Long
2023-02-23 19:27 ` Jonathan Corbet
0 siblings, 2 replies; 3+ messages in thread
From: Lukas Bulwahn @ 2023-02-20 16:57 UTC (permalink / raw)
To: Peter Zijlstra, Ingo Molnar, Will Deacon, Waiman Long,
Boqun Feng, Jonathan Corbet, linux-doc
Cc: kernel-janitors, linux-kernel, Lukas Bulwahn
The config is actually called CONFIG_RT_MUTEXES, not CONFIG_RT_MUTEX.
The config CONFIG_LOCK_TORTURE_TEST should be connected by underscore, for
the sake of consistent referencing to configs in the kernel documentation.
Address those issues.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
Documentation/locking/locktorture.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/locking/locktorture.rst b/Documentation/locking/locktorture.rst
index dfaf9fc883f4..7f56fc0d7c31 100644
--- a/Documentation/locking/locktorture.rst
+++ b/Documentation/locking/locktorture.rst
@@ -5,7 +5,7 @@ Kernel Lock Torture Test Operation
CONFIG_LOCK_TORTURE_TEST
========================
-The CONFIG LOCK_TORTURE_TEST config option provides a kernel module
+The CONFIG_LOCK_TORTURE_TEST config option provides a kernel module
that runs torture tests on core kernel locking primitives. The kernel
module, 'locktorture', may be built after the fact on the running
kernel to be tested, if desired. The tests periodically output status
@@ -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.
--
2.17.1
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] docs: locking: refer to the actual existing config names
2023-02-20 16:57 [PATCH] docs: locking: refer to the actual existing config names Lukas Bulwahn
@ 2023-02-20 17:18 ` Waiman Long
2023-02-23 19:27 ` Jonathan Corbet
1 sibling, 0 replies; 3+ messages in thread
From: Waiman Long @ 2023-02-20 17:18 UTC (permalink / raw)
To: Lukas Bulwahn, Peter Zijlstra, Ingo Molnar, Will Deacon,
Boqun Feng, Jonathan Corbet, linux-doc
Cc: kernel-janitors, linux-kernel
On 2/20/23 11:57, Lukas Bulwahn wrote:
> The config is actually called CONFIG_RT_MUTEXES, not CONFIG_RT_MUTEX.
>
> The config CONFIG_LOCK_TORTURE_TEST should be connected by underscore, for
> the sake of consistent referencing to configs in the kernel documentation.
>
> Address those issues.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Documentation/locking/locktorture.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/locking/locktorture.rst b/Documentation/locking/locktorture.rst
> index dfaf9fc883f4..7f56fc0d7c31 100644
> --- a/Documentation/locking/locktorture.rst
> +++ b/Documentation/locking/locktorture.rst
> @@ -5,7 +5,7 @@ Kernel Lock Torture Test Operation
> CONFIG_LOCK_TORTURE_TEST
> ========================
>
> -The CONFIG LOCK_TORTURE_TEST config option provides a kernel module
> +The CONFIG_LOCK_TORTURE_TEST config option provides a kernel module
> that runs torture tests on core kernel locking primitives. The kernel
> module, 'locktorture', may be built after the fact on the running
> kernel to be tested, if desired. The tests periodically output status
> @@ -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@redhat.com>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] docs: locking: refer to the actual existing config names
2023-02-20 16:57 [PATCH] docs: locking: refer to the actual existing config names Lukas Bulwahn
2023-02-20 17:18 ` Waiman Long
@ 2023-02-23 19:27 ` Jonathan Corbet
1 sibling, 0 replies; 3+ messages in thread
From: Jonathan Corbet @ 2023-02-23 19:27 UTC (permalink / raw)
To: Lukas Bulwahn, Peter Zijlstra, Ingo Molnar, Will Deacon,
Waiman Long, Boqun Feng, linux-doc
Cc: kernel-janitors, linux-kernel, Lukas Bulwahn
Lukas Bulwahn <lukas.bulwahn@gmail.com> writes:
> The config is actually called CONFIG_RT_MUTEXES, not CONFIG_RT_MUTEX.
>
> The config CONFIG_LOCK_TORTURE_TEST should be connected by underscore, for
> the sake of consistent referencing to configs in the kernel documentation.
>
> Address those issues.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Documentation/locking/locktorture.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/locking/locktorture.rst b/Documentation/locking/locktorture.rst
> index dfaf9fc883f4..7f56fc0d7c31 100644
> --- a/Documentation/locking/locktorture.rst
> +++ b/Documentation/locking/locktorture.rst
> @@ -5,7 +5,7 @@ Kernel Lock Torture Test Operation
> CONFIG_LOCK_TORTURE_TEST
> ========================
>
> -The CONFIG LOCK_TORTURE_TEST config option provides a kernel module
> +The CONFIG_LOCK_TORTURE_TEST config option provides a kernel module
> that runs torture tests on core kernel locking primitives. The kernel
> module, 'locktorture', may be built after the fact on the running
> kernel to be tested, if desired. The tests periodically output status
> @@ -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.
>
Applied, thanks.
jon
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-02-23 19:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-20 16:57 [PATCH] docs: locking: refer to the actual existing config names Lukas Bulwahn
2023-02-20 17:18 ` Waiman Long
2023-02-23 19:27 ` Jonathan Corbet
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).