Lockdep doesn't have to be made to work with crossrelease and just works
with them. Reword the title so that what the option does is clear.
Signed-off-by: Byungchul Park <byungchul.p...@lge.com>
---
lib/Kconfig.debug | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 84bb4c5..444bb7b 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -1156,7 +1156,7 @@ config LOCK_STAT
(CONFIG_LOCKDEP defines "acquire" and "release" events.)
config LOCKDEP_CROSSRELEASE
- bool "Lock debugging: make lockdep work for crosslocks"
+ bool "Lock debugging: enable cross-locking checks in lockdep"
help
This makes lockdep work for crosslock which is a lock allowed to
be released in a different context from the acquisition context.
--
1.9.1
