From: Steven Lung <1030steven@gmail.com>
To: mingo@redhat.com
Cc: peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com, vschneid@redhat.com,
linux-kernel@vger.kernel.org, 1030steven@gmail.com
Subject: [PATCH] sched/fair: Make 'enqueue' spelling consistent
Date: Thu, 9 Jun 2022 14:57:17 +0800 [thread overview]
Message-ID: <20220609065717.81547-1-1030steven@gmail.com> (raw)
In this file, there are two types of spelling for the word 'enqueue'
in present continuous: 'enqueueing' and 'enqueuing'. 'Enqueuing' is
used more than the other, so I replaced all the 'enqueueing' to
'enqueuing' for making the spelling in this file consistent.
Signed-off-by: Steven Lung <1030steven@gmail.com>
---
kernel/sched/fair.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 77b2048a9..37317710d 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -1000,7 +1000,7 @@ update_stats_enqueue_fair(struct cfs_rq *cfs_rq, struct sched_entity *se, int fl
return;
/*
- * Are we enqueueing a waiting task? (for current tasks
+ * Are we enqueuing a waiting task? (for current tasks
* a dequeue/enqueue event is a NOP)
*/
if (se != cfs_rq->curr)
@@ -1018,7 +1018,7 @@ update_stats_dequeue_fair(struct cfs_rq *cfs_rq, struct sched_entity *se, int fl
return;
/*
- * Mark the end of the wait period if dequeueing a
+ * Mark the end of the wait period if dequeuing a
* waiting task:
*/
if (se != cfs_rq->curr)
@@ -3920,7 +3920,7 @@ static inline void update_load_avg(struct cfs_rq *cfs_rq, struct sched_entity *s
* !last_update_time means we've passed through
* migrate_task_rq_fair() indicating we migrated.
*
- * IOW we're enqueueing a task on a new CPU.
+ * IOW we're enqueuing a task on a new CPU.
*/
attach_entity_load_avg(cfs_rq, se);
update_tg_load_avg(cfs_rq);
--
2.35.1
reply other threads:[~2022-06-09 6:58 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=20220609065717.81547-1-1030steven@gmail.com \
--to=1030steven@gmail.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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