From: "tip-bot for T.Zhou" <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: torvalds@linux-foundation.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, t1zhou@163.com, mingo@kernel.org,
peterz@infradead.org, hpa@zytor.com
Subject: [tip:sched/core] sched/dl: Fix comment in pick_next_task_dl()
Date: Wed, 23 Nov 2016 01:27:53 -0800 [thread overview]
Message-ID: <tip-176cedc4ed143745708999155c11b5717cdebb35@git.kernel.org> (raw)
In-Reply-To: <20161123004832.GA2983@geo>
Commit-ID: 176cedc4ed143745708999155c11b5717cdebb35
Gitweb: http://git.kernel.org/tip/176cedc4ed143745708999155c11b5717cdebb35
Author: T.Zhou <t1zhou@163.com>
AuthorDate: Wed, 23 Nov 2016 08:48:32 +0800
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Wed, 23 Nov 2016 10:23:21 +0100
sched/dl: Fix comment in pick_next_task_dl()
Fix cut & paste oversight:
s/pull_rt_task/pull_dl_task
Signed-off-by: T.Zhou <t1zhou@163.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: juri.lelli@gmail.com
Link: http://lkml.kernel.org/r/20161123004832.GA2983@geo
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
kernel/sched/deadline.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
index c61b461..70ef2b1 100644
--- a/kernel/sched/deadline.c
+++ b/kernel/sched/deadline.c
@@ -1137,7 +1137,7 @@ pick_next_task_dl(struct rq *rq, struct task_struct *prev, struct pin_cookie coo
pull_dl_task(rq);
lockdep_repin_lock(&rq->lock, cookie);
/*
- * pull_rt_task() can drop (and re-acquire) rq->lock; this
+ * pull_dl_task() can drop (and re-acquire) rq->lock; this
* means a stop task can slip in, in which case we need to
* re-start task selection.
*/
prev parent reply other threads:[~2016-11-23 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 0:48 [PATCH] sched/dl: change pull_rt_task() to pull_dl_task() in comment T.Zhou
2016-11-23 9:27 ` tip-bot for T.Zhou [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-176cedc4ed143745708999155c11b5717cdebb35@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=peterz@infradead.org \
--cc=t1zhou@163.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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