Commit-ID: e6beaa363d56d7fc2f8cd6f7291e4d93911a428a
Gitweb: http://git.kernel.org/tip/e6beaa363d56d7fc2f8cd6f7291e4d93911a428a
Author: Tom(JeHyeon) Yeon <tom.y...@windriver.com>
AuthorDate: Wed, 18 Mar 2015 14:03:30 +0900
Committer: Ingo Molnar <mi...@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.y...@windriver.com>
Cc: pet...@infradead.org
Link:
http://lkml.kernel.org/r/1426655010-31651-1-git-send-email-tom.y...@windriver.com
Signed-off-by: Ingo Molnar <mi...@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)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
