[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1513266622-15860-7-git-send-email-baiyaowei@cmss.chinamobile.com>
Date: Thu, 14 Dec 2017 10:50:21 -0500
From: Yaowei Bai <baiyaowei@...s.chinamobile.com>
To: akpm@...ux-foundation.org, rdunlap@...radead.org,
rientjes@...gle.com, joe@...ches.com
Cc: linux-kernel@...r.kernel.org, baiyaowei@...s.chinamobile.com
Subject: [PATCH 6/7] kernel/mutex: mutex_is_locked can be boolean
This patch makes mutex_is_locked return bool due to this
particular function only using either one or zero as its return
value.
No functional change.
Signed-off-by: Yaowei Bai <baiyaowei@...s.chinamobile.com>
---
include/linux/mutex.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/mutex.h b/include/linux/mutex.h
index 153274f..f25c134 100644
--- a/include/linux/mutex.h
+++ b/include/linux/mutex.h
@@ -138,9 +138,9 @@ extern void __mutex_init(struct mutex *lock, const char *name,
* mutex_is_locked - is the mutex locked
* @lock: the mutex to be queried
*
- * Returns 1 if the mutex is locked, 0 if unlocked.
+ * Returns true if the mutex is locked, false if unlocked.
*/
-static inline int mutex_is_locked(struct mutex *lock)
+static inline bool mutex_is_locked(struct mutex *lock)
{
/*
* XXX think about spin_is_locked
--
1.8.3.1
Powered by blists - more mailing lists