Messages in this thread Patch in this message | | | From | Mukesh Ojha <> | Subject | [PATCH 2/2 v2] locking/mutex: Use mutex flags macro instead of hard code value | Date | Tue, 30 Jul 2019 21:19:54 +0530 |
| |
Use the mutex flag macro instead of hard code value inside __mutex_owner().
Signed-off-by: Mukesh Ojha <mojha@codeaurora.org> --- Changes in v2: - Framed the commit according the changes done in 1/2 of the patchset.
kernel/locking/mutex.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c index f73250a..1c8f86a 100644 --- a/kernel/locking/mutex.c +++ b/kernel/locking/mutex.c @@ -72,7 +72,7 @@ */ static inline struct task_struct *__mutex_owner(struct mutex *lock) { - return (struct task_struct *)(atomic_long_read(&lock->owner) & ~0x07); + return (struct task_struct *)(atomic_long_read(&lock->owner) & ~MUTEX_FLAGS); } /** -- Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
| |