Commit-ID: 0f0a22260d613b4ee3f483ee1ea6fa27f92a9e40 Gitweb: http://git.kernel.org/tip/0f0a22260d613b4ee3f483ee1ea6fa27f92a9e40 Author: Byungchul Park <[email protected]> AuthorDate: Thu, 17 Aug 2017 17:57:40 +0900 Committer: Ingo Molnar <[email protected]> CommitDate: Thu, 17 Aug 2017 11:38:55 +0200
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 <[email protected]> Cc: Linus Torvalds <[email protected]> Cc: Peter Zijlstra <[email protected]> Cc: Thomas Gleixner <[email protected]> Cc: [email protected] Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Ingo Molnar <[email protected]> --- lib/Kconfig.debug | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index 1ad7f1b..8fb8a20 100644 --- 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.
