public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] rtmutex: Cleanup the variable's name in rt_mutex_adjust_prio_chain
@ 2015-03-18  5:03 Tom(JeHyeon) Yeon
  2015-03-25 12:45 ` [tip:locking/core] locking/rtmutex: Rename argument in the rt_mutex_adjust_prio_chain() documentation as well tip-bot for Tom(JeHyeon) Yeon
  0 siblings, 1 reply; 2+ messages in thread
From: Tom(JeHyeon) Yeon @ 2015-03-18  5:03 UTC (permalink / raw)
  To: peterz, mingo; +Cc: linux-kernel, Tom(JeHyeon) Yeon

From: "Tom(JeHyeon) Yeon" <tom.yeon@windriver.com>

change "deadlock_detect" to "chwalk" following by commit 8930ed80

Signed-off-by: Tom(JeHyeon) Yeon <tom.yeon@windriver.com>
---
 kernel/locking/rtmutex.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
index 6357265..b732793 100644
--- a/kernel/locking/rtmutex.c
+++ b/kernel/locking/rtmutex.c
@@ -349,7 +349,7 @@ static inline struct rt_mutex *task_blocked_on_lock(struct task_struct *p)
  *
  * @task:	the task owning the mutex (owner) for which a chain walk is
  *		probably needed
- * @deadlock_detect: do we have to carry out deadlock detection?
+ * @chwalk:	do we have to carry out deadlock detection?
  * @orig_lock:	the mutex (can be NULL if we are walking the chain to recheck
  *		things for a task that has just got its priority adjusted, and
  *		is waiting on a mutex)
-- 
1.7.9.5


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

* [tip:locking/core] locking/rtmutex: Rename argument in the rt_mutex_adjust_prio_chain() documentation as well
  2015-03-18  5:03 [PATCH] rtmutex: Cleanup the variable's name in rt_mutex_adjust_prio_chain Tom(JeHyeon) Yeon
@ 2015-03-25 12:45 ` tip-bot for Tom(JeHyeon) Yeon
  0 siblings, 0 replies; 2+ messages in thread
From: tip-bot for Tom(JeHyeon) Yeon @ 2015-03-25 12:45 UTC (permalink / raw)
  To: linux-tip-commits; +Cc: linux-kernel, mingo, hpa, tom.yeon, tglx

Commit-ID:  e6beaa363d56d7fc2f8cd6f7291e4d93911a428a
Gitweb:     http://git.kernel.org/tip/e6beaa363d56d7fc2f8cd6f7291e4d93911a428a
Author:     Tom(JeHyeon) Yeon <tom.yeon@windriver.com>
AuthorDate: Wed, 18 Mar 2015 14:03:30 +0900
Committer:  Ingo Molnar <mingo@kernel.org>
CommitDate: Wed, 25 Mar 2015 13:43:55 +0100

locking/rtmutex: Rename argument in the rt_mutex_adjust_prio_chain() documentation as well

The following commit changed "deadlock_detect" to "chwalk":

   8930ed80f970 ("rtmutex: Cleanup deadlock detector debug logic")

do that rename in the function's documentation as well.

Signed-off-by: Tom(JeHyeon) Yeon <tom.yeon@windriver.com>
Cc: peterz@infradead.org
Link: http://lkml.kernel.org/r/1426655010-31651-1-git-send-email-tom.yeon@windriver.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
 kernel/locking/rtmutex.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
index e16e554..c0b8e9d 100644
--- a/kernel/locking/rtmutex.c
+++ b/kernel/locking/rtmutex.c
@@ -349,7 +349,7 @@ static inline struct rt_mutex *task_blocked_on_lock(struct task_struct *p)
  *
  * @task:	the task owning the mutex (owner) for which a chain walk is
  *		probably needed
- * @deadlock_detect: do we have to carry out deadlock detection?
+ * @chwalk:	do we have to carry out deadlock detection?
  * @orig_lock:	the mutex (can be NULL if we are walking the chain to recheck
  *		things for a task that has just got its priority adjusted, and
  *		is waiting on a mutex)

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

end of thread, other threads:[~2015-03-25 12:45 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-03-18  5:03 [PATCH] rtmutex: Cleanup the variable's name in rt_mutex_adjust_prio_chain Tom(JeHyeon) Yeon
2015-03-25 12:45 ` [tip:locking/core] locking/rtmutex: Rename argument in the rt_mutex_adjust_prio_chain() documentation as well tip-bot for Tom(JeHyeon) Yeon

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