From: Randy Dunlap <rdunlap@infradead.org>
To: Costa Shulyupin <costa.shul@redhat.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
rcu@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v1] doc: RCU: Fix typo
Date: Thu, 27 Aug 2026 09:37:11 -0700 [thread overview]
Message-ID: <9f2abc12-a3c0-482a-b5d4-57b129db10fa@infradead.org> (raw)
In-Reply-To: <20260827090506.1172620-1-costa.shul@redhat.com>
On 8/27/26 2:05 AM, Costa Shulyupin wrote:
> strategem -> stratagem.
>
> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/RCU/Design/Requirements/Requirements.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/RCU/Design/Requirements/Requirements.rst b/Documentation/RCU/Design/Requirements/Requirements.rst
> index 8101fe6229d5..b10e0484ae13 100644
> --- a/Documentation/RCU/Design/Requirements/Requirements.rst
> +++ b/Documentation/RCU/Design/Requirements/Requirements.rst
> @@ -1442,7 +1442,7 @@ periods:
> corresponding CPU's next scheduling-clock.
> #. CPUs mentioned in the ``nohz_full`` kernel boot parameter can run
> indefinitely in the kernel without scheduling-clock interrupts, which
> - defeats the above need_resched() strategem. RCU will therefore
> + defeats the above need_resched() stratagem. RCU will therefore
> invoke resched_cpu() on any ``nohz_full`` CPUs still holding out
> after 109 milliseconds.
> #. In kernels built with ``CONFIG_RCU_BOOST=y``, if a given task that
--
~Randy
next prev parent reply other threads:[~2026-08-27 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 9:05 Costa Shulyupin
2026-08-27 16:37 ` Randy Dunlap [this message]
2026-08-27 18:06 ` Paul E. McKenney
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=9f2abc12-a3c0-482a-b5d4-57b129db10fa@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.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®