Commit 0f0a2226 authored by Byungchul Park's avatar Byungchul Park Committed by Ingo Molnar

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: default avatarByungchul 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.comSigned-off-by: default avatarIngo Molnar <mingo@kernel.org>
parent d0541b0f
...@@ -1153,7 +1153,7 @@ config LOCK_STAT ...@@ -1153,7 +1153,7 @@ config LOCK_STAT
(CONFIG_LOCKDEP defines "acquire" and "release" events.) (CONFIG_LOCKDEP defines "acquire" and "release" events.)
config LOCKDEP_CROSSRELEASE config LOCKDEP_CROSSRELEASE
bool "Lock debugging: make lockdep work for crosslocks" bool "Lock debugging: enable cross-locking checks in lockdep"
help help
This makes lockdep work for crosslock which is a lock allowed to This makes lockdep work for crosslock which is a lock allowed to
be released in a different context from the acquisition context. be released in a different context from the acquisition context.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment