From: "xiaofeng.yan" <xiaofeng.yan@huawei.com>
To: <linux-kernel@vger.kernel.org>, <mingo@redhat.com>,
<peterz@infradead.org>
Cc: <xiaofeng_yan2004@126.com>, "xiaofeng.yan" <xiaofeng.yan@huawei.com>
Subject: [PATCH] sched/rt: Fix a comment in struct sched_dl_entity
Date: Fri, 9 May 2014 03:21:27 +0000 [thread overview]
Message-ID: <1399605687-18094-1-git-send-email-xiaofeng.yan@huawei.com> (raw)
Change sched_setscheduler2() to sched_setattr() in the comments.
There isn't function sched_setscheduler2() in the main line.
The previous EDF version defines this function
before being merged into the main line.
User should use sched_setattr() instead of
sched_setscheduler2() now.
Signed-off-by: xiaofeng.yan <xiaofeng.yan@huawei.com>
---
include/linux/sched.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/sched.h b/include/linux/sched.h
index 25f54c7..ed64468 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -1123,8 +1123,8 @@ struct sched_dl_entity {
/*
* Original scheduling parameters. Copied here from sched_attr
- * during sched_setscheduler2(), they will remain the same until
- * the next sched_setscheduler2().
+ * during sched_setattr(), they will remain the same until
+ * the next sched_setattr().
*/
u64 dl_runtime; /* maximum runtime for each instance */
u64 dl_deadline; /* relative deadline of each instance */
--
1.7.9.5
next reply other threads:[~2014-05-09 3:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 3:21 xiaofeng.yan [this message]
2014-05-19 13:10 ` [tip:sched/core] " tip-bot for xiaofeng.yan
2014-05-22 12:28 ` [tip:sched/core] sched/rt: Fix 'struct sched_dl_entity' and dl_task_time() comments, to match the current upstream code tip-bot for xiaofeng.yan
-- strict thread matches above, loose matches on Subject: below --
2014-05-08 10:31 [PATCH] sched/rt: Fix a comment in struct sched_dl_entity xiaofeng.yan
2014-05-08 11:04 ` Peter Zijlstra
2014-05-09 3:33 ` xiaofeng.yan
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=1399605687-18094-1-git-send-email-xiaofeng.yan@huawei.com \
--to=xiaofeng.yan@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=xiaofeng_yan2004@126.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®