[patch 8/8] lock validator: add s390 to supported options

[Heiko Carstens]

From: Heiko Carstens <heiko.carstens@xxxxxxxxxx>

Enable DEBUG_SPINLOCK_ALLOC, DEBUG_RWLOCK_ALLOC, DEBUG_MUTEX_ALLOC,
DEBUG_RWSEM_ALLOC and LOCKDEP for s390.

Signed-off-by: Heiko Carstens <heiko.carstens@xxxxxxxxxx>
---

 lib/Kconfig.debug |   10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff -purN a/lib/Kconfig.debug b/lib/Kconfig.debug
--- a/lib/Kconfig.debug	2006-06-14 12:54:17.000000000 +0200
+++ b/lib/Kconfig.debug	2006-06-14 13:46:17.000000000 +0200
@@ -175,7 +175,7 @@ config DEBUG_SPINLOCK
 
 config DEBUG_SPINLOCK_ALLOC
 	bool "Spinlock debugging: detect incorrect freeing of live spinlocks"
-	depends on DEBUG_SPINLOCK && X86
+	depends on DEBUG_SPINLOCK && (X86 || S390)
 	select LOCKDEP
 	help
 	 This feature will check whether any held spinlock is incorrectly
@@ -224,7 +224,7 @@ config PROVE_SPIN_LOCKING
 
 config DEBUG_RWLOCK_ALLOC
 	bool "rw-lock debugging: detect incorrect freeing of live rwlocks"
-	depends on DEBUG_SPINLOCK && X86
+	depends on DEBUG_SPINLOCK && (X86 || S390)
 	select LOCKDEP
 	help
 	 This feature will check whether any held rwlock is incorrectly
@@ -281,7 +281,7 @@ config DEBUG_MUTEXES
 
 config DEBUG_MUTEX_ALLOC
 	bool "Mutex debugging: detect incorrect freeing of live mutexes"
-	depends on DEBUG_MUTEXES && X86
+	depends on DEBUG_MUTEXES && (X86 || S390)
 	select LOCKDEP
 	help
 	 This feature will check whether any held mutex is incorrectly
@@ -337,7 +337,7 @@ config DEBUG_RWSEMS
 
 config DEBUG_RWSEM_ALLOC
 	bool "rwsem debugging: detect incorrect freeing of live rwsems"
-	depends on DEBUG_RWSEMS && X86
+	depends on DEBUG_RWSEMS && (X86 || S390)
 	select LOCKDEP
 	help
 	 This feature will check whether any held rwsem is incorrectly
@@ -389,7 +389,7 @@ config LOCKDEP
 	select FRAME_POINTER
 	select KALLSYMS
 	select KALLSYMS_ALL
-	depends on X86
+	depends on X86 || S390
 
 config DEBUG_NON_NESTED_UNLOCKS
 	bool "Detect non-nested unlocks"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/