From: Ke Ma <makebit1999@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: tj@kernel.org, arighi@nvidia.com, void@manifault.com,
changwoo@igalia.com, Ke Ma <makebit1999@gmail.com>
Subject: [PATCH] kernel/sched/ext.c: fix typo "occured" -> "occurred" in comments
Date: Thu, 19 Jun 2025 23:11:28 +0200 [thread overview]
Message-ID: <20250619211128.2193-1-makebit1999@gmail.com> (raw)
Fixes a minor spelling mistake in two comment lines
Signed-off-by: Ke Ma <makebit1999@gmail.com>
---
kernel/sched/ext.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/ext.c b/kernel/sched/ext.c
index b498d867ba21..d312b950cbf4 100644
--- a/kernel/sched/ext.c
+++ b/kernel/sched/ext.c
@@ -1637,7 +1637,7 @@ static struct task_struct *scx_task_iter_next_locked(struct scx_task_iter *iter)
* scx_add_event - Increase an event counter for 'name' by 'cnt'
* @sch: scx_sched to account events for
* @name: an event name defined in struct scx_event_stats
- * @cnt: the number of the event occured
+ * @cnt: the number of the event occurred
*
* This can be used when preemption is not disabled.
*/
@@ -1650,7 +1650,7 @@ static struct task_struct *scx_task_iter_next_locked(struct scx_task_iter *iter)
* __scx_add_event - Increase an event counter for 'name' by 'cnt'
* @sch: scx_sched to account events for
* @name: an event name defined in struct scx_event_stats
- * @cnt: the number of the event occured
+ * @cnt: the number of the event occurred
*
* This should be used only when preemption is disabled.
*/
--
2.44.0.windows.1
next reply other threads:[~2025-06-19 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 21:11 Ke Ma [this message]
2025-06-23 18:11 ` [PATCH] kernel/sched/ext.c: fix typo "occured" -> "occurred" in comments Tejun Heo
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=20250619211128.2193-1-makebit1999@gmail.com \
--to=makebit1999@gmail.com \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=void@manifault.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 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.