From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Quchaosheng <quchaosheng000406@163.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] docs: kernel-parameters: fix a truncated sentence for preempt=lazy
Date: Wed, 23 Sep 2026 09:31:58 +0200 [thread overview]
Message-ID: <20260923073158.ik4UOBAo@linutronix.de> (raw)
In-Reply-To: <20260922083101.99685-2-quchaosheng000406@163.com>
On 2026-09-22 16:31:01 [+0800], Quchaosheng wrote:
> The "lazy" entry ends with:
>
> One preemption is when the task returns to user space.
>
> which is not a sentence. It is a leftover from shortening "One such
> preemption is when the task returns to user space."
>
> Writing it as "preemption point" reads better than restoring the missing
> word, so use that.
>
> Fixes: f66e4a996582 ("sched/core: Update kernel boot parameters for LAZY preempt.")
> Assisted-by: LLM
> Suggested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Signed-off-by: Quchaosheng <quchaosheng000406@163.com>
Reviewed-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Sebastian
next prev parent reply other threads:[~2026-09-23 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 8:31 [PATCH v2 1/2] sched/doc: add a preemption model overview Quchaosheng
2026-09-22 8:31 ` [PATCH v2 2/2] docs: kernel-parameters: fix a truncated sentence for preempt=lazy Quchaosheng
2026-09-23 7:31 ` Sebastian Andrzej Siewior [this message]
2026-09-23 7:28 ` [PATCH v2 1/2] sched/doc: add a preemption model overview Sebastian Andrzej Siewior
2026-09-26 15:45 ` Jonathan Corbet
2026-09-28 2:36 ` [PATCH] Documentation: sched-preemption: Add a SPDX license identifier Quchaosheng
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=20260923073158.ik4UOBAo@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=quchaosheng000406@163.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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 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.