Linux Documentation
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Karl Mehltretter <kmehltretter@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	Thomas Gleixner <tglx@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] docs: cpu_hotplug: Fix multi-instance removal calls
Date: Sat, 22 Aug 2026 10:25:15 -0700	[thread overview]
Message-ID: <2c4fc25e-e38e-483c-ad75-1aa421bd7bb1@infradead.org> (raw)
In-Reply-To: <20260822121651.1559-2-kmehltretter@gmail.com>



On 8/22/26 5:16 AM, Karl Mehltretter wrote:
> The function is named cpuhp_state_remove_instance(), not
> cpuhp_remove_instance().
> 
> Fixes: c9871c800f65 ("Documentation: core-api/cpuhotplug: Rewrite the API section")
> Assisted-by: Codex:gpt-5.6-sol
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.

> ---
>  Documentation/core-api/cpu_hotplug.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/core-api/cpu_hotplug.rst b/Documentation/core-api/cpu_hotplug.rst
> index 6de26d1c6a9ad..f8b3f59a3d5f7 100644
> --- a/Documentation/core-api/cpu_hotplug.rst
> +++ b/Documentation/core-api/cpu_hotplug.rst
> @@ -607,9 +607,9 @@ ONLINE section for notifications on online and offline operation::
>     if (ret)
>          return ret;
>     ....
> -   cpuhp_remove_instance(state, &inst1->node);
> +   cpuhp_state_remove_instance(state, &inst1->node);
>     ....
> -   cpuhp_remove_instance(state, &inst2->node);
> +   cpuhp_state_remove_instance(state, &inst2->node);
>     ....
>     cpuhp_remove_multi_state(state);
>  

-- 
~Randy

  reply	other threads:[~2026-08-22 17:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 12:16 [PATCH 0/7] docs: core-api: Fix stale function names and a broken example Karl Mehltretter
2026-08-22 12:16 ` [PATCH 1/7] docs: cpu_hotplug: Fix multi-instance removal calls Karl Mehltretter
2026-08-22 17:25   ` Randy Dunlap [this message]
2026-08-24 16:57   ` Jonathan Corbet
2026-08-24 18:05     ` Karl Mehltretter
2026-08-24 18:28       ` Jonathan Corbet
2026-08-22 12:16 ` [PATCH 2/7] docs: irq-affinity: Restore grep in example Karl Mehltretter
2026-08-22 17:25   ` Randy Dunlap
2026-08-22 12:16 ` [PATCH 3/7] docs: dma-attributes: Fix dma_alloc_attrs() name Karl Mehltretter
2026-08-22 17:25   ` Randy Dunlap
2026-08-24  9:26   ` Marek Szyprowski
2026-08-22 12:16 ` [PATCH 4/7] docs: swiotlb: Fix maximum mapping size helper Karl Mehltretter
2026-08-22 17:26   ` Randy Dunlap
2026-08-22 12:16 ` [PATCH 5/7] docs: this_cpu_ops: Fix SRCU helper names Karl Mehltretter
2026-08-22 16:39   ` Paul E. McKenney
2026-08-22 17:28   ` Randy Dunlap
     [not found] ` <20260822121651.1559-7-kmehltretter@gmail.com>
2026-08-22 12:28   ` [PATCH 6/7] docs: xarray: Fix xas_try_split() name Zi Yan
2026-08-22 17:30   ` Randy Dunlap
     [not found] ` <20260822121651.1559-8-kmehltretter@gmail.com>
2026-08-22 17:32   ` [PATCH 7/7] docs: debugobjects: Fix debug_object_init() name Randy Dunlap

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=2c4fc25e-e38e-483c-ad75-1aa421bd7bb1@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=kmehltretter@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tglx@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