mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Phil Auld <pauld@redhat.com>
To: Christian Loehle <christian.loehle@arm.com>
Cc: Jianyun Gao <jianyungao89@gmail.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Valentin Schneider <vschneid@redhat.com>
Subject: Re: [PATCH v2] sched: Fix some spelling mistakes in the scheduler module
Date: Tue, 30 Sep 2025 08:29:59 -0400	[thread overview]
Message-ID: <20250930122959.GA87275@pauld.westford.csb> (raw)
In-Reply-To: <ff4099fa-a6e4-4478-af81-a4c1baaf483b@arm.com>

On Tue, Sep 30, 2025 at 09:26:59AM +0100 Christian Loehle wrote:
> On 9/29/25 07:12, Jianyun Gao wrote:
> > From: "jianyun.gao" <jianyungao89@gmail.com>
> > 
> > The following are some spelling mistakes existing in the scheduler
> > module. Just fix it!
> > 
> >   slection -> selection
> >   achitectures -> architectures
> >   excempt -> except
> >   incorectly -> incorrectly
> >   litle -> little
> >   faireness -> fairness
> >   condtion -> condition
> > 
> > Signed-off-by: jianyun.gao <jianyungao89@gmail.com>
> > ---
> > V2:
> > Delete the incorrect modifications for "borken" in V1.
> > The previous version is here:
> > 
> > https://lore.kernel.org/lkml/20250926092832.1457477-1-jianyungao89@gmail.com/
> > 
> >  kernel/sched/core.c     | 2 +-
> >  kernel/sched/cputime.c  | 2 +-
> >  kernel/sched/fair.c     | 8 ++++----
> >  kernel/sched/wait_bit.c | 2 +-
> >  4 files changed, 7 insertions(+), 7 deletions(-)
> > 
> > diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> > index 7f1e5cb94c53..af5076e40567 100644
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -6858,7 +6858,7 @@ static void __sched notrace __schedule(int sched_mode)
> >  		/*
> >  		 * We pass task_is_blocked() as the should_block arg
> >  		 * in order to keep mutex-blocked tasks on the runqueue
> > -		 * for slection with proxy-exec (without proxy-exec
> > +		 * for selection with proxy-exec (without proxy-exec
> >  		 * task_is_blocked() will always be false).
> >  		 */
> >  		try_to_block_task(rq, prev, &prev_state,
> > diff --git a/kernel/sched/cputime.c b/kernel/sched/cputime.c
> > index 7097de2c8cda..2429be5a5e40 100644
> > --- a/kernel/sched/cputime.c
> > +++ b/kernel/sched/cputime.c
> > @@ -585,7 +585,7 @@ void cputime_adjust(struct task_cputime *curr, struct prev_cputime *prev,
> >  	stime = mul_u64_u64_div_u64(stime, rtime, stime + utime);
> >  	/*
> >  	 * Because mul_u64_u64_div_u64() can approximate on some
> > -	 * achitectures; enforce the constraint that: a*b/(b+c) <= a.
> > +	 * architectures; enforce the constraint that: a*b/(b+c) <= a.
> >  	 */
> >  	if (unlikely(stime > rtime))
> >  		stime = rtime;
> > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> > index 18a30ae35441..20fe5899b247 100644
> > --- a/kernel/sched/fair.c
> > +++ b/kernel/sched/fair.c
> > @@ -5381,7 +5381,7 @@ dequeue_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int flags)
> >  		bool delay = sleep;
> >  		/*
> >  		 * DELAY_DEQUEUE relies on spurious wakeups, special task
> > -		 * states must not suffer spurious wakeups, excempt them.
> > +		 * states must not suffer spurious wakeups, except them.
> 
> This should be exempt, no?
> 

I had the same thought then decded that "except" as a verb worked too.
We are making an exception for the special states, right? I think either
works, but not both at once :) 

But that said, I'm not sure we should bother as these don't seem to
effect the meaning (at least to me as a native 'merican speaker). 

Cheers,
Phil



-- 


  parent reply	other threads:[~2025-09-30 12:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29  6:12 Jianyun Gao
2025-09-30  8:26 ` Christian Loehle
2025-09-30 12:27   ` Jianyun Gao
2025-09-30 12:29   ` Phil Auld [this message]
2025-09-30 13:11     ` Jianyun Gao
  -- strict thread matches above, loose matches on Subject: below --
2025-09-26 11:00 [PATCH] " Peter Zijlstra
2025-09-26 16:25 ` [PATCH v2] " jianyun.gao

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=20250930122959.GA87275@pauld.westford.csb \
    --to=pauld@redhat.com \
    --cc=bsegall@google.com \
    --cc=christian.loehle@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=jianyungao89@gmail.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

all inboxes | Powered by JetHome®