when down_interruptible fail, means a signal occur, or any other failure
we are panicing, and it seems that we should not panic, instead we would
have done a spinlock, but currently removing the panic call.

Signed-off-by: Devendra Naga <[email protected]>
---
 drivers/staging/csr/csr_framework_ext.c |    1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/staging/csr/csr_framework_ext.c 
b/drivers/staging/csr/csr_framework_ext.c
index e203f60..e62878e 100644
--- a/drivers/staging/csr/csr_framework_ext.c
+++ b/drivers/staging/csr/csr_framework_ext.c
@@ -82,7 +82,6 @@ CsrResult CsrMutexLock(CsrMutexHandle *mutexHandle)
 
     if (down_interruptible(mutexHandle))
     {
-        CsrPanic(CSR_TECH_FW, CSR_PANIC_FW_UNEXPECTED_VALUE, "CsrMutexLock 
Failed");
         return CSR_FE_RESULT_INVALID_POINTER;
     }
 
-- 
1.7.9.5

_______________________________________________
devel mailing list
[email protected]
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel

Reply via email to