public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Ryan Cheevers <cheeversr0@gmail.com>, linux-doc@vger.kernel.org
Cc: skhan@linuxfoundation.org, longman@redhat.com,
	frederic@kernel.org, cheeversr0@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: fix typo in housekeeping
Date: Mon, 09 Mar 2026 09:55:26 -0600	[thread overview]
Message-ID: <878qc1xaj5.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260309060015.2349939-1-cheeversr0@gmail.com>

Ryan Cheevers <cheeversr0@gmail.com> writes:

> Signed-off-by: Ryan Cheevers <cheeversr0@gmail.com>
> ---
>  Documentation/core-api/housekeeping.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/core-api/housekeeping.rst b/Documentation/core-api/housekeeping.rst
> index e5417302774c..92c6e53cea75 100644
> --- a/Documentation/core-api/housekeeping.rst
> +++ b/Documentation/core-api/housekeeping.rst
> @@ -15,7 +15,7 @@ various deferrals etc...
>  Sometimes housekeeping is just some unbound work (unbound workqueues,
>  unbound timers, ...) that gets easily assigned to non-isolated CPUs.
>  But sometimes housekeeping is tied to a specific CPU and requires
> -elaborated tricks to be offloaded to non-isolated CPUs (RCU_NOCB, remote
> +elaborate tricks to be offloaded to non-isolated CPUs (RCU_NOCB, remote
>  scheduler tick, etc...).

Applied, thanks.

jon

      reply	other threads:[~2026-03-09 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09  6:00 [PATCH] docs: fix typo in housekeeping Ryan Cheevers
2026-03-09 15:55 ` Jonathan Corbet [this message]

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=878qc1xaj5.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=cheeversr0@gmail.com \
    --cc=frederic@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox