locking/lockdep: Reword title of LOCKDEP_CROSSRELEASE config

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.park@lge.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: kernel-team@lge.com
Link: http://lkml.kernel.org/r/1502960261-16206-2-git-send-email-byungchul.park@lge.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 1ad7f1b..8fb8a20 100644 (file)
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -1153,7 +1153,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.