From: Alessio Balsini <balsini@android.com>
To: linux-kernel@vger.kernel.org
Cc: kernel-team@android.com, Alessio Balsini <balsini@android.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH] sched/deadline: Minor typos in dl_entity_overflow comment
Date: Tue, 28 May 2019 16:08:40 +0100 [thread overview]
Message-ID: <20190528150840.65581-1-balsini@android.com> (raw)
Fix two non-critical typos in the documentation of the dl_entity_overflow
function:
- "rather then" --> "rather than";
- "in such way that" --> "in such a way that".
Signed-off-by: Alessio Balsini <balsini@android.com>
---
kernel/sched/deadline.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
index 43901fa3f2693..9b3987b74ca64 100644
--- a/kernel/sched/deadline.c
+++ b/kernel/sched/deadline.c
@@ -769,7 +769,7 @@ static bool dl_entity_overflow(struct sched_dl_entity *dl_se,
}
/*
- * Revised wakeup rule [1]: For self-suspending tasks, rather then
+ * Revised wakeup rule [1]: For self-suspending tasks, rather than
* re-initializing task's runtime and deadline, the revised wakeup
* rule adjusts the task's runtime to avoid the task to overrun its
* density.
@@ -780,7 +780,7 @@ static bool dl_entity_overflow(struct sched_dl_entity *dl_se,
* Therefore, runtime can be adjusted to:
* runtime = (dl_runtime / dl_deadline) * (deadline - t)
*
- * In such way that runtime will be equal to the maximum density
+ * In such a way that runtime will be equal to the maximum density
* the task can use without breaking any rule.
*
* [1] Luca Abeni, Giuseppe Lipari, and Juri Lelli. 2015. Constant
--
2.22.0.rc1.257.g3120a18244-goog
reply other threads:[~2019-05-28 15:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190528150840.65581-1-balsini@android.com \
--to=balsini@android.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®