CONFIG_PROVE_SPIN_LOCKING, CONFIG_PROVE_RW_LOCKING,
CONFIG_PROVE_MUTEX_LOCKING and CONFIG_PROVE_RWSEM_LOCKING have never
existed in mainline. Lock proving was merged as the single
CONFIG_PROVE_LOCKING, which has depended on CONFIG_TRACE_IRQFLAGS_SUPPORT
from the start, so there is no reduced set of options without it.

Fixes: 55df314fbdb4 ("[PATCH] lockdep: irqtrace subsystem, docs")
Assisted-by: LLM
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
---
 Documentation/core-api/irq/irqflags-tracing.rst | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/Documentation/core-api/irq/irqflags-tracing.rst b/Documentation/core-api/irq/irqflags-tracing.rst
index bdd208259fb3..a3c77046ae6b 100644
--- a/Documentation/core-api/irq/irqflags-tracing.rst
+++ b/Documentation/core-api/irq/irqflags-tracing.rst
@@ -9,12 +9,8 @@ that it gives interested subsystems an opportunity to be notified of
 every hardirqs-off/hardirqs-on, softirqs-off/softirqs-on event that
 happens in the kernel.
 
-CONFIG_TRACE_IRQFLAGS_SUPPORT is needed for CONFIG_PROVE_SPIN_LOCKING
-and CONFIG_PROVE_RW_LOCKING to be offered by the generic lock debugging
-code. Otherwise only CONFIG_PROVE_MUTEX_LOCKING and
-CONFIG_PROVE_RWSEM_LOCKING will be offered on an architecture - these
-are locking APIs that are not used in IRQ context. (the one exception
-for rwsems is worked around)
+CONFIG_TRACE_IRQFLAGS_SUPPORT is needed for CONFIG_PROVE_LOCKING to be
+offered by the generic lock debugging code.
 
 Architecture support for this is certainly not in the "trivial"
 category, because lots of lowlevel assembly code deal with irq-flags
-- 
2.53.0

Karl Mehltretter <kmehltretter@gmail.com> writes:

> CONFIG_PROVE_SPIN_LOCKING, CONFIG_PROVE_RW_LOCKING,
> CONFIG_PROVE_MUTEX_LOCKING and CONFIG_PROVE_RWSEM_LOCKING have never
> existed in mainline. Lock proving was merged as the single
> CONFIG_PROVE_LOCKING, which has depended on CONFIG_TRACE_IRQFLAGS_SUPPORT
> from the start, so there is no reduced set of options without it.
>
> Fixes: 55df314fbdb4 ("[PATCH] lockdep: irqtrace subsystem, docs")
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
> ---
>  Documentation/core-api/irq/irqflags-tracing.rst | 8 ++------
>  1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/core-api/irq/irqflags-tracing.rst b/Documentation/core-api/irq/irqflags-tracing.rst
> index bdd208259fb3..a3c77046ae6b 100644
> --- a/Documentation/core-api/irq/irqflags-tracing.rst
> +++ b/Documentation/core-api/irq/irqflags-tracing.rst
> @@ -9,12 +9,8 @@ that it gives interested subsystems an opportunity to be notified of
>  every hardirqs-off/hardirqs-on, softirqs-off/softirqs-on event that
>  happens in the kernel.
>  
> -CONFIG_TRACE_IRQFLAGS_SUPPORT is needed for CONFIG_PROVE_SPIN_LOCKING
> -and CONFIG_PROVE_RW_LOCKING to be offered by the generic lock debugging
> -code. Otherwise only CONFIG_PROVE_MUTEX_LOCKING and
> -CONFIG_PROVE_RWSEM_LOCKING will be offered on an architecture - these
> -are locking APIs that are not used in IRQ context. (the one exception
> -for rwsems is worked around)
> +CONFIG_TRACE_IRQFLAGS_SUPPORT is needed for CONFIG_PROVE_LOCKING to be
> +offered by the generic lock debugging code.

Applied, thanks.

jon