From: Tom(JeHyeon) Yeon Date: Wed, 18 Mar 2015 05:03:30 +0000 (+0900) Subject: locking/rtmutex: Rename argument in the rt_mutex_adjust_prio_chain() documentation... X-Git-Tag: v4.1-rc1~186^2~5 X-Git-Url: https://git.karo-electronics.de/?a=commitdiff_plain;h=e6beaa363d56d7fc2f8cd6f7291e4d93911a428a;p=karo-tx-linux.git 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 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 --- diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c index e16e5542bf13..c0b8e9db6b2e 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)