All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH v2] sched: Fixes typos in comments
@ 2025-02-02 15:32 Atul Kumar Pant
  0 siblings, 0 replies; only message in thread
From: Atul Kumar Pant @ 2025-02-02 15:32 UTC (permalink / raw)
  To: mingo, peterz, juri.lelli, vincent.guittot
  Cc: Atul Kumar Pant, dietmar.eggemann, rostedt, bsegall, mgorman,
	vschneid, linux-kernel

Fixes spelling errors in the comments.

Signed-off-by: Atul Kumar Pant <atulpant.linux@gmail.com>
---

changes since v1:
  added changelog
  removed an incorrect fix

 kernel/sched/core.c     | 2 +-
 kernel/sched/cputime.c  | 2 +-
 kernel/sched/wait_bit.c | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 3e5a6bf58..451e30249 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -8998,7 +8998,7 @@ void sched_release_group(struct task_group *tg)
 	 * that tg_unthrottle_up() won't add decayed cfs_rq's to it.
 	 *
 	 * We therefore defer calling unregister_fair_sched_group() to
-	 * sched_unregister_group() which is guarantied to get called only after the
+	 * sched_unregister_group() which is guaranteed to get called only after the
 	 * current RCU grace period has expired.
 	 */
 	spin_lock_irqsave(&task_group_lock, flags);
diff --git a/kernel/sched/cputime.c b/kernel/sched/cputime.c
index 0bed0fa1a..f8ada8239 100644
--- a/kernel/sched/cputime.c
+++ b/kernel/sched/cputime.c
@@ -584,7 +584,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/wait_bit.c b/kernel/sched/wait_bit.c
index b410b61ce..4197f5ed2 100644
--- a/kernel/sched/wait_bit.c
+++ b/kernel/sched/wait_bit.c
@@ -204,7 +204,7 @@ EXPORT_SYMBOL(init_wait_var_entry);
  * given variable to change.  wait_var_event() can be waiting for an
  * arbitrary condition to be true and associates that condition with an
  * address.  Calling wake_up_var() suggests that the condition has been
- * made true, but does not strictly require the condtion to use the
+ * made true, but does not strictly require the condition to use the
  * address given.
  *
  * The wake-up is sent to tasks in a waitqueue selected by hash from a
-- 
2.34.1


^ permalink raw reply related	[flat|nested] only message in thread

only message in thread, other threads:[~2025-02-02 15:32 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-02-02 15:32 [PATCH v2] sched: Fixes typos in comments Atul Kumar Pant

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.