Correct "upto" to "up to", reported by scripts/checkpatch.pl using the
misspelling list in scripts/spelling.txt.  Only touches comments, no code
changes.

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.
 	 * 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
-- 
2.48.1

Hello,

Applied to wq/for-7.4.

Thanks.
-- 
tejun

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/