mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tom(JeHyeon) Yeon" <tomyeon750415lkml@gmail.com>
To: peterz@infradead.org, mingo@redhat.com
Cc: linux-kernel@vger.kernel.org,
	"Tom(JeHyeon) Yeon" <tom.yeon@windriver.com>
Subject: [PATCH] rtmutex: Cleanup the variable's name in rt_mutex_adjust_prio_chain
Date: Wed, 18 Mar 2015 14:03:30 +0900	[thread overview]
Message-ID: <1426655010-31651-1-git-send-email-tom.yeon@windriver.com> (raw)

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


             reply	other threads:[~2015-03-18  5:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18  5:03 Tom(JeHyeon) Yeon [this message]
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

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=1426655010-31651-1-git-send-email-tom.yeon@windriver.com \
    --to=tomyeon750415lkml@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®