From: "tip-bot for Tom(JeHyeon) Yeon" <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org, hpa@zytor.com,
tom.yeon@windriver.com, tglx@linutronix.de
Subject: [tip:locking/core] locking/rtmutex: Rename argument in the rt_mutex_adjust_prio_chain() documentation as well
Date: Wed, 25 Mar 2015 05:45:37 -0700 [thread overview]
Message-ID: <tip-e6beaa363d56d7fc2f8cd6f7291e4d93911a428a@git.kernel.org> (raw)
In-Reply-To: <1426655010-31651-1-git-send-email-tom.yeon@windriver.com>
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)
prev parent reply other threads:[~2015-03-25 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tip-e6beaa363d56d7fc2f8cd6f7291e4d93911a428a@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=tom.yeon@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.