[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240921071501.263450-1-dolinux.peng@gmail.com>
Date: Sat, 21 Sep 2024 15:15:01 +0800
From: Donglin Peng <dolinux.peng@...il.com>
To: dmitry.torokhov@...il.com
Cc: javier.carrasco.cruz@...il.com,
kees@...nel.org,
linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org,
Donglin Peng <dolinux.peng@...il.com>
Subject: [PATCH] Input: ims-pcu - fix a mutex usage error
The mutex_lock_interruptible should be switched to scoped_cond_guard(mutex_intr, ...)
instead of scoped_cond_guard(mutex, ..).
Fixes: 703f12672e1f ("Input: ims-pcu - switch to using cleanup functions")
Signed-off-by: Donglin Peng <dolinux.peng@...il.com>
---
drivers/input/misc/ims-pcu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/misc/ims-pcu.c b/drivers/input/misc/ims-pcu.c
index c086dadb45e3..058f3470b7ae 100644
--- a/drivers/input/misc/ims-pcu.c
+++ b/drivers/input/misc/ims-pcu.c
@@ -1067,7 +1067,7 @@ static ssize_t ims_pcu_attribute_store(struct device *dev,
if (data_len > attr->field_length)
return -EINVAL;
- scoped_cond_guard(mutex, return -EINTR, &pcu->cmd_mutex) {
+ scoped_cond_guard(mutex_intr, return -EINTR, &pcu->cmd_mutex) {
memset(field, 0, attr->field_length);
memcpy(field, buf, data_len);
--
2.25.1
Powered by blists - more mailing lists