summaryrefslogtreecommitdiff
path: root/kernel/sched
diff options
context:
space:
mode:
authorxiaofeng.yan <xiaofeng.yan@huawei.com>2014-07-07 05:59:04 +0000
committerIngo Molnar <mingo@kernel.org>2014-07-16 13:38:20 +0200
commit1b09d29bc00964d9032d80516f958044ac6b3805 (patch)
tree5e24c57b513ae555eb600828c5874b13ccb0ca13 /kernel/sched
parent8875125efe8402c4d84b08291e68f1281baba8e2 (diff)
sched/rt: Fix replenish_dl_entity() comments to match the current upstream code
Signed-off-by: xiaofeng.yan <xiaofeng.yan@huawei.com> Signed-off-by: Peter Zijlstra <peterz@infradead.org> Link: http://lkml.kernel.org/r/1404712744-16986-1-git-send-email-xiaofeng.yan@huawei.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'kernel/sched')
-rw-r--r--kernel/sched/deadline.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
index df0b77a8caca..255ce138b652 100644
--- a/kernel/sched/deadline.c
+++ b/kernel/sched/deadline.c
@@ -306,7 +306,7 @@ static inline void setup_new_dl_entity(struct sched_dl_entity *dl_se,
* the overrunning entity can't interfere with other entity in the system and
* can't make them miss their deadlines. Reasons why this kind of overruns
* could happen are, typically, a entity voluntarily trying to overcome its
- * runtime, or it just underestimated it during sched_setscheduler_ex().
+ * runtime, or it just underestimated it during sched_setattr().
*/
static void replenish_dl_entity(struct sched_dl_entity *dl_se,
struct sched_dl_entity *pi_se)