public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] kernel/locking: mutex: simplify access to the first entry in the wait-list
@ 2013-12-12  9:45 Andrzej Pietrasiewicz
  2013-12-12  9:53 ` Peter Zijlstra
  2013-12-12 12:46 ` Ingo Molnar
  0 siblings, 2 replies; 4+ messages in thread
From: Andrzej Pietrasiewicz @ 2013-12-12  9:45 UTC (permalink / raw)
  To: linux-kernel
  Cc: Andrzej Pietrasiewicz, Kyungmin Park, Marek Szyprowski,
	Peter Zijlstra, Ingo Molnar

Use list_first_entry instead of explicitly accessing the first entry
with "head".next. The comment one line above becomes obsolete.

Signed-off-by: Andrzej Pietrasiewicz <andrzej.p@samsung.com>
Signed-off-by: Kyungmin Park <andrzej.p@samsung.com>
---
 kernel/locking/mutex.c |    5 ++---
 1 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c
index 4dd6e4c..4af4f9c 100644
--- a/kernel/locking/mutex.c
+++ b/kernel/locking/mutex.c
@@ -730,10 +730,9 @@ __mutex_unlock_common_slowpath(atomic_t *lock_count, int nested)
 		atomic_set(&lock->count, 1);
 
 	if (!list_empty(&lock->wait_list)) {
-		/* get the first entry from the wait-list: */
 		struct mutex_waiter *waiter =
-				list_entry(lock->wait_list.next,
-					   struct mutex_waiter, list);
+				list_first_entry(&lock->wait_list,
+						 struct mutex_waiter, list);
 
 		debug_mutex_wake_waiter(lock, waiter);
 
-- 
1.7.0.4


^ permalink raw reply related	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2013-12-12 12:46 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-12  9:45 [PATCH] kernel/locking: mutex: simplify access to the first entry in the wait-list Andrzej Pietrasiewicz
2013-12-12  9:53 ` Peter Zijlstra
2013-12-12 11:28   ` Andrzej Pietrasiewicz
2013-12-12 12:46 ` Ingo Molnar

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox