[tip: sched/core] sched/deadline: Fix a typo in a comment

[tip-bot2 for Christophe JAILLET]

The following commit has been merged into the sched/core branch of tip:

Commit-ID:     c49694173da004b1b16082f82f28bd625415fbb2
Gitweb:        https://git.kernel.org/tip/c49694173da004b1b16082f82f28bd625415fbb2
Author:        Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
AuthorDate:    Tue, 02 Jun 2020 21:50:02 +02:00
Committer:     Peter Zijlstra <peterz@xxxxxxxxxxxxx>
CommitterDate: Mon, 15 Jun 2020 14:10:06 +02:00

sched/deadline: Fix a typo in a comment

s/deadine/deadline/

Signed-off-by: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
Signed-off-by: Peter Zijlstra (Intel) <peterz@xxxxxxxxxxxxx>
Link: https://lkml.kernel.org/r/20200602195002.677448-1-christophe.jaillet@xxxxxxxxxx
---
 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 84e84ba..d4708e2 100644
--- a/kernel/sched/deadline.c
+++ b/kernel/sched/deadline.c
@@ -1137,7 +1137,7 @@ void init_dl_task_timer(struct sched_dl_entity *dl_se)
  * cannot use the runtime, and so it replenishes the task. This rule
  * works fine for implicit deadline tasks (deadline == period), and the
  * CBS was designed for implicit deadline tasks. However, a task with
- * constrained deadline (deadine < period) might be awakened after the
+ * constrained deadline (deadline < period) might be awakened after the
  * deadline, but before the next period. In this case, replenishing the
  * task would allow it to run for runtime / deadline. As in this case
  * deadline < period, CBS enables a task to run for more than the