From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] docs: kdoc_parser: allow __exit in function prototypes
Date: Fri, 6 Feb 2026 09:31:07 +0100 [thread overview]
Message-ID: <20260206093101.39c06f0d@foz.lan> (raw)
In-Reply-To: <20260206065440.2412185-1-rdunlap@infradead.org>
On Thu, 5 Feb 2026 22:54:40 -0800
Randy Dunlap <rdunlap@infradead.org> wrote:
> 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>
Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.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 +"), ""),
> (KernRe(r"__flatten +"), ""),
> (KernRe(r"__meminit +"), ""),
Thanks,
Mauro
next prev parent reply other threads:[~2026-02-06 8:31 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 [this message]
2026-02-09 19:50 ` Jonathan Corbet
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=20260206093101.39c06f0d@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=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