From: Bradley Morgan <brads@mainlining.org>
To: hemanth.selam@gmail.com
Cc: jiangshanlai@gmail.com, linux-kernel@vger.kernel.org, tj@kernel.org
Subject: Re: [PATCH] kernel: fix typo "upto" in comment
Date: Mon, 07 Sep 2026 09:07:31 +0100 [thread overview]
Message-ID: <F6979DEC-40D5-442C-8FE7-CDD697172A20@mainlining.org> (raw)
In-Reply-To: <20260907062338.10890-1-hemanth.selam@gmail.com>
On 7 September 2026 07:23:38 BST, Hemanth Selam <hemanth.selam@gmail.com>
wrote:
>Correct "upto" to "up to", reported by scripts/checkpatch.pl using the
>misspelling list in scripts/spelling.txt. Only touches comments, no code
>changes.
Ok.
>
>Assisted-by: Cursor:claude-opus-5
>Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
>---
> kernel/workqueue.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/kernel/workqueue.c b/kernel/workqueue.c
>index 1ae3732a2c51..b6afb7cee661 100644
>--- a/kernel/workqueue.c
>+++ b/kernel/workqueue.c
>@@ -8264,7 +8264,7 @@ static void __init wq_cpu_intensive_thresh_init(void)
> * lot slower CPUs including microcontrollers where the threshold is way
> * too low.
> *
>- * Let's scale up the threshold upto 1 second if BogoMips is below 4000.
>+ * Let's scale up the threshold up to 1 second if BogoMips is below 4000.
Really.
Sigh.
> * This is by no means accurate but it doesn't have to be. The mechanism
> * is still useful even when the threshold is fully scaled up. Also, as
> * the reports would usually be applicable to everyone, some machines
>
--- Thanks!
https://lore.kernel.org/all/EE579805-42F2-4C58-B752-F28779EEB717@grrlz.net/
next prev parent reply other threads:[~2026-09-07 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 6:23 Hemanth Selam
2026-09-07 8:07 ` Bradley Morgan [this message]
2026-09-08 17:13 ` 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=F6979DEC-40D5-442C-8FE7-CDD697172A20@mainlining.org \
--to=brads@mainlining.org \
--cc=hemanth.selam@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
/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®