mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: kernel-doc: include "define" as an identifier type
Date: Tue, 15 Sep 2026 13:01:20 -0600	[thread overview]
Message-ID: <87eceu9w5b.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260912055202.103573-1-rdunlap@infradead.org>

Randy Dunlap <rdunlap@infradead.org> writes:

> Update the list of identifier types to include "define", which was
> added in 2014 in commit
> cbb4d3e6510b ("scripts/kernel-doc: handle object-like macros")
>
> Fixes: 91a3d6be99e6 ("doc-guide: kernel-doc: tell about object-like macros")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Shuah Khan <skhan@linuxfoundation.org>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: linux-doc@vger.kernel.org
>
>  Documentation/doc-guide/kernel-doc.rst |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-next-20260911.orig/Documentation/doc-guide/kernel-doc.rst
> +++ linux-next-20260911/Documentation/doc-guide/kernel-doc.rst
> @@ -565,8 +565,8 @@ identifiers: *[ function/type ...]*
>    Include documentation for each *function* and *type* in *source*.
>    If no *function* is specified, the documentation for all functions
>    and types in the *source* will be included.
> -  *type* can be a ``struct``, ``union``, ``enum``, ``typedef`` or ``var``
> -  identifier.
> +  *type* can be a ``struct``, ``union``, ``enum``, ``typedef``, ``var``,
> +  or ``define`` identifier.

Applied, thanks.

jon

      reply	other threads:[~2026-09-15 19:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12  5:52 Randy Dunlap
2026-09-15 19:01 ` 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=87eceu9w5b.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rdunlap@infradead.org \
    --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

all inboxes | Powered by JetHome®