mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Sakurai Shun <ssh1326@icloud.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Cc: Sakurai Shun <ssh1326@icloud.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: fix typo in list.rst
Date: Mon, 25 May 2026 14:22:10 -0600	[thread overview]
Message-ID: <87zf1nz1cd.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260517040714.8024-1-ssh1326@icloud.com>

Sakurai Shun <ssh1326@icloud.com> writes:

> Replace "reinitalizes" with "reinitializes"
>
> Signed-off-by: Sakurai Shun <ssh1326@icloud.com>
> ---
>  Documentation/core-api/list.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/core-api/list.rst b/Documentation/core-api/list.rst
> index 241464ca0..4819343a2 100644
> --- a/Documentation/core-api/list.rst
> +++ b/Documentation/core-api/list.rst
> @@ -752,7 +752,7 @@ This is because list_splice() did not reinitialize the list_head it took
>  entries from, leaving its pointer pointing into what is now a different list.
>  
>  If we want to avoid this situation, list_splice_init() can be used. It does the
> -same thing as list_splice(), except reinitalizes the donor list_head after the
> +same thing as list_splice(), except reinitializes the donor list_head after the
>  transplant.

This one was fixed a month ago; please work against docs-next (or
linux-next) when generating patches.

Thanks,

jon

      reply	other threads:[~2026-05-25 20:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-17  4:07 Sakurai Shun
2026-05-25 20:22 ` 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=87zf1nz1cd.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=ssh1326@icloud.com \
    /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

Powered by JetHome