linux-kernel - Re: [PATCH] sched/psi.c: Rudimentary typo fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 26 Mar 2021 19:41:22 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Johannes Weiner <hannes@...xchg.org>
Cc:     Bhaskar Chowdhury <unixbhaskar@...il.com>, mingo@...hat.com,
        juri.lelli@...hat.com, vincent.guittot@...aro.org,
        dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
        mgorman@...e.de, bristot@...hat.com, linux-kernel@...r.kernel.org,
        rdunlap@...radead.org
Subject: Re: [PATCH] sched/psi.c: Rudimentary typo fixes

On Fri, Mar 26, 2021 at 02:00:18PM -0400, Johannes Weiner wrote:
> On Fri, Mar 26, 2021 at 06:12:33PM +0530, Bhaskar Chowdhury wrote:
> > 
> > s/possible/possible/
> > s/ exceution/execution/
> > s/manupulations/manipulations/
> > 
> > Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
> > ---
> >  kernel/sched/psi.c | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/kernel/sched/psi.c b/kernel/sched/psi.c
> > index 967732c0766c..316ebc57a115 100644
> > --- a/kernel/sched/psi.c
> > +++ b/kernel/sched/psi.c
> > @@ -59,7 +59,7 @@
> >   * states, we would have to conclude a CPU SOME pressure number of
> >   * 100%, since *somebody* is waiting on a runqueue at all
> >   * times. However, that is clearly not the amount of contention the
> > - * workload is experiencing: only one out of 256 possible exceution
> > + * workload is experiencing: only one out of 256 possible execution
> 
> I thought this was the french spelling.
> 
> Joking aside, the corrections look right, but I also had no trouble
> understanding what those sentences mean. Typos happen, plus we have a
> lot of non-native speakers who won't use perfect spelling or grammar.
> 
> So for me, the bar is "this can be easily understood", not "needs to
> be perfect English", and I'd say let's skip patches like these unless
> they fix something truly unintelligble.

Ignore this robot, lots of people already have a special mail rule for
him. On top of that, this spelling mistake was already fixed by Ingo in:

 3b03706fa621 ("sched: Fix various typos")

Which is part of a series of such patches to head off the endless,
mindless, stream of this.