From d2b43e6302fad00eab4a3e017bf47ca56bcfd3d1 Mon Sep 17 00:00:00 2001
From: Nicholas Mc Guire <der.herr@hofr.at>
Date: Sun, 15 Dec 2013 15:40:47 +0100
Subject: bad return value in __mutex_lock_check_stamp

Bad return value in _mutex_lock_check_stamp - this problem only would show
up with 3.12.1 rt4 applied but CONFIG_PREEMPT_RT_FULL not enabled
currently it would be returning what ever vprintk_emit ended up with
(atleast on x86), which probably is not the intended behavior. Added a
return 0; as in the case with CONFIG_PREEMPT_RT_FULL enabled.

Signed-off-by: Nicholas Mc Guire <der.herr@hofr.at>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>

diff --git a/kernel/rtmutex.c b/kernel/rtmutex.c
index 1bb34e9..d3d0c72 100644
--- a/kernel/rtmutex.c
+++ b/kernel/rtmutex.c
@@ -989,6 +989,7 @@ static inline int __sched
 __mutex_lock_check_stamp(struct rt_mutex *lock, struct ww_acquire_ctx *ctx)
 {
 	BUG();
+	return 0;
 }
 
 #endif
-- 
cgit v0.10.2