Re: [PATCH] sched,psi: fix typo in comment

[Joe Perches]

On Mon, 2021-03-29 at 09:35 +0200, Peter Zijlstra wrote:
> On Sat, Mar 27, 2021 at 08:46:10PM +0800, Xie XiuQi wrote:
> > s/exceution/execution/
> > s/possibe/possible/
> > s/manupulations/manipulations/
> > 
> > Signed-off-by: Xie XiuQi 
> 
> Xie, if you'd have bothered to check the development tree of the code
> you're patching, you'd have found it's long since fixed.

March 18, 2021 doesn't seem a long time ago to me.

commit 3b03706fa621ce31a3e9ef6307020fde4e6aae16
Author: Ingo Molnar 
Date:   Thu Mar 18 13:38:50 2021 +0100

sched: Fix various typos

> I'm getting sick and tired of people wasting bandwidth with this
> nonsense.

This seems more like a large overreaction IMO.

Re: [PATCH] sched,psi: fix typo in comment

[Peter Zijlstra]

On Sat, Mar 27, 2021 at 08:46:10PM +0800, Xie XiuQi wrote:
> s/exceution/execution/
> s/possibe/possible/
> s/manupulations/manipulations/
> 
> Signed-off-by: Xie XiuQi 

Xie, if you'd have bothered to check the development tree of the code
you're patching, you'd have found it's long since fixed.

Can we please get a MAINTAINERS entry that indicates the willingness to
suffer nonsense like this? Then checkpatch will tell people to bugger
off and I can stop blacklisting people on this.

I'm getting sick and tired of people wasting bandwidth with this
nonsense.

[PATCH] sched,psi: fix typo in comment

[Xie XiuQi]

s/exceution/execution/
s/possibe/possible/
s/manupulations/manipulations/

Signed-off-by: Xie XiuQi 
---
 kernel/sched/psi.c | 7 ---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/kernel/sched/psi.c b/kernel/sched/psi.c
index 967732c0766c..7c800be47c6f 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
  * threads will be contended at any given time, or about 0.4%.
  *
  * Conversely, consider a scenario of 4 tasks and 4 CPUs where at any
@@ -73,7 +73,7 @@
  * we have to base our calculation on the number of non-idle tasks in
  * conjunction with the number of available CPUs, which is the number
  * of potential execution threads. SOME becomes then the proportion of
- * delayed tasks to possibe threads, and FULL is the share of possible
+ * delayed tasks to possible threads, and FULL is the share of possible
  * threads that are unproductive due to delays:
  *
  * threads = min(nr_nonidle_tasks, nr_cpus)
@@ -441,7 +441,8 @@ static void psi_avgs_work(struct work_struct *work)
mutex_unlock(>avgs_lock);
 }
 
-/* Trigger tracking window manupulations */
+/* Trigger tracking window manipulations */
+
 static void window_reset(struct psi_window *win, u64 now, u64 value,
 u64 prev_growth)
 {
-- 
2.25.1