public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-doc@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] docs: kdoc_parser: allow __exit in function prototypes
Date: Mon, 09 Feb 2026 12:50:13 -0700	[thread overview]
Message-ID: <87ecmt8znu.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260206065440.2412185-1-rdunlap@infradead.org>

Randy Dunlap <rdunlap@infradead.org> writes:

> Handle functions that are marked with __exit to prevent warnings:
>
> Documentation/networking/iucv:35: ../net/iucv/iucv.c:1918: WARNING: Error in declarator or parameters
> Invalid C declaration: Expecting "(" in parameters. [error at 12]
>   void __exit iucv_exit (void)
>   ------------^
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Shuah Khan <skhan@linuxfoundation.org>
>
>  tools/lib/python/kdoc/kdoc_parser.py |    1 +
>  1 file changed, 1 insertion(+)
>
> --- linux-next-20260204.orig/tools/lib/python/kdoc/kdoc_parser.py
> +++ linux-next-20260204/tools/lib/python/kdoc/kdoc_parser.py
> @@ -176,6 +176,7 @@ function_xforms  = [
>      (KernRe(r"^__FORTIFY_INLINE +"), ""),
>      (KernRe(r"__init +"), ""),
>      (KernRe(r"__init_or_module +"), ""),
> +    (KernRe(r"__exit +"), ""),
>      (KernRe(r"__deprecated +"), ""),

Applied, thanks.

jon

      parent reply	other threads:[~2026-02-09 19:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06  6:54 [PATCH] docs: kdoc_parser: allow __exit in function prototypes Randy Dunlap
2026-02-06  8:31 ` Mauro Carvalho Chehab
2026-02-09 19:50 ` 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=87ecmt8znu.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@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