From: Randy Dunlap <rdunlap@infradead.org>
To: Karl Mehltretter <kmehltretter@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] docs: debugobjects: Fix debug_object_init() name
Date: Sat, 22 Aug 2026 10:32:22 -0700 [thread overview]
Message-ID: <a77cd90d-c52b-4865-a9ea-fd73129b42ff@infradead.org> (raw)
In-Reply-To: <20260822121651.1559-8-kmehltretter@gmail.com>
On 8/22/26 5:16 AM, Karl Mehltretter wrote:
> The initialization helper is debug_object_init(), not
> debug_objects_init().
>
> Fixes: 691cc54c7d28 ("debugobjects: add documentation")
> 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/debug-objects.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/core-api/debug-objects.rst b/Documentation/core-api/debug-objects.rst
> index ac926fd55a64a..708775fc581b7 100644
> --- a/Documentation/core-api/debug-objects.rst
> +++ b/Documentation/core-api/debug-objects.rst
> @@ -129,7 +129,7 @@ When the real object is not yet tracked by debugobjects then the
> fixup_activate function is called if available. This is necessary to
> allow the legitimate activation of statically allocated and initialized
> objects. The fixup function checks whether the object is valid and calls
> -the debug_objects_init() function to initialize the tracking of this
> +the debug_object_init() function to initialize the tracking of this
> object.
>
> When the activation is legitimate, then the state of the associated
--
~Randy
prev parent reply other threads:[~2026-08-22 17:32 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
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 ` Randy Dunlap [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=a77cd90d-c52b-4865-a9ea-fd73129b42ff@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.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