mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: pr4veensingh@proton.me,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: memory-hotplug: fix typo 'fo' -> 'for' in NODE_ADDED_FIRST_MEMORY description
Date: Tue, 17 Mar 2026 08:42:50 -0600	[thread overview]
Message-ID: <875x6uecut.fsf@trenco.lwn.net> (raw)
In-Reply-To: <by7jSPCep0WcWKD6nntH0wGbcN59hRhsEOc2lHBps2QizxRtedH25CdW8DO33YiqJU3Y7kGWesJnBts-jvgMzNqDvLWH3cTDYpJPuNed9hU=@proton.me>

pr4veensingh@proton.me writes:

> From cf0fb033799f1766841d876728f52ee84c89c676 Mon Sep 17 00:00:00 2001
> From: Praveen Kumar Singh <pr4veensingh@proton.me>
> Date: Tue, 17 Mar 2026 11:10:32 +0530
> Subject: [PATCH] docs: memory-hotplug: fix typo 'fo' -> 'for' in
>  NODE_ADDED_FIRST_MEMORY description

Please do not include the above in the patch body; the maintainer just
has to strip it out.  I have done that this time.

> The description of NODE_ADDED_FIRST_MEMORY notification contains
> a missing 'r' in the word 'for'. Fix the typo.
>
> Signed-off-by: Praveen Kumar Singh <pr4veensingh@proton.me>
> ---
>  Documentation/core-api/memory-hotplug.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/core-api/memory-hotplug.rst b/Documentation/core-api/memory-hotplug.rst
> index 8fc97c237..46b0490f5 100644
> --- a/Documentation/core-api/memory-hotplug.rst
> +++ b/Documentation/core-api/memory-hotplug.rst
> @@ -96,7 +96,7 @@ NODE_CANCEL_ADDING_FIRST_MEMORY
>   Generated if NODE_ADDING_FIRST_MEMORY fails.
>
>  NODE_ADDED_FIRST_MEMORY
> - Generated when memory has become available fo this node for the first time.
> + Generated when memory has become available for this node for the first time.
>
Applied, thanks.

jon

      reply	other threads:[~2026-03-17 14:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17  5:53 pr4veensingh
2026-03-17 14:42 ` 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=875x6uecut.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pr4veensingh@proton.me \
    /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®