rtmutex: Cleanup the variable's name in rt_mutex_adjust_prio_chain
PATCH 1/1 rtmutex: Cleanup the variable's name in rt_mutex_adjust_prio_chain
From: "Tom(JeHyeon) Yeon" <[email protected]>
change "deadlock_detect" to "chwalk" following by commit 8930ed80
Signed-off-by Tom(JeHyeon) Yeon <[email protected]>
--- kernel/locking/rtmutex.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/locking/rtmutex.c +1 -1
@@ -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)
Signature · 1 line
1.7.9.5
tip-bot for Tom(JeHyeon) Yeon
merge bot[tip:locking/core] locking/rtmutex: Rename argument in the rt_mutex_adjust_prio_chain() documentation as well
locking/rtmutex: Rename argument in the rt_mutex_adjust_prio_chain() documentation as well
Commit-ID: e6beaa363d56d7fc2f8cd6f7291e4d93911a428a Gitweb: http://git.kernel.org/tip/e6beaa363d56d7fc2f8cd6f7291e4d93911a428a Author: Tom(JeHyeon) Yeon <[email protected]> AuthorDate: Wed, 18 Mar 2015 14:03:30 +0900 Committer: Ingo Molnar <[email protected]> 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 <[email protected]>
Signed-off-by Ingo Molnar <[email protected]>
--- kernel/locking/rtmutex.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/locking/rtmutex.c +1 -1
@@ -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)