From: Joe Perches <joe@perches.com>
To: Barry Song <21cnbao@gmail.com>,
akpm@linux-foundation.org, linux-doc@vger.kernel.org,
workflows@vger.kernel.org
Cc: apw@canonical.com, broonie@kernel.org, chenhuacai@loongson.cn,
chris@zankel.net, corbet@lwn.net, dwaipayanray1@gmail.com,
herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org,
linux@roeck-us.net, lukas.bulwahn@gmail.com,
mac.xxn@outlook.com, sfr@canb.auug.org.au,
v-songbaohua@oppo.com, Max Filippov <jcmvbkbc@gmail.com>,
Jeff Johnson <quic_jjohnson@quicinc.com>,
Charlemagne Lasse <charlemagnelasse@gmail.com>
Subject: Re: [PATCH v5 2/2] scripts: checkpatch: check unused parameters for function-like macro
Date: Sun, 31 Mar 2024 19:37:09 -0700 [thread overview]
Message-ID: <f5bb12d8602a03d28b2a8aeaffd8f74f001d692d.camel@perches.com> (raw)
In-Reply-To: <20240401012120.6052-3-21cnbao@gmail.com>
On Mon, 2024-04-01 at 14:21 +1300, Barry Song wrote:
> From: Xining Xu <mac.xxn@outlook.com>
>
> If function-like macros do not utilize a parameter, it might result in a
> build warning. In our coding style guidelines, we advocate for utilizing
> static inline functions to replace such macros. This patch verifies
> compliance with the new rule.
>
> For a macro such as the one below,
>
> #define test(a) do { } while (0)
>
> The test result is as follows.
>
> ERROR: Parameter 'a' is not used in function-like macro, please use static
> inline instead
> #21: FILE: mm/init-mm.c:20:
> +#define test(a) do { } while (0)
This is no longer true.
Please update the ERROR->WARN and message as below
Ideally, this would have an update to
Documentation/dev-tools/checkpatch.rst
to describe the new --verbose message type
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -6040,6 +6040,12 @@ sub process {
> CHK("MACRO_ARG_PRECEDENCE",
> "Macro argument '$arg' may be better as '($arg)' to avoid precedence issues\n" . "$herectx");
> }
> +
> +# check if this is an unused argument
> + if ($define_stmt !~ /\b$arg\b/) {
> + WARN("MACRO_ARG_UNUSED",
> + "Argument '$arg' is not used in function-like macro\n" . "$herectx");
> + }
next prev parent reply other threads:[~2024-04-01 2:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 1:21 [PATCH v5 0/2] codingstyle: avoid unused parameters for a " Barry Song
2024-04-01 1:21 ` [PATCH v5 1/2] Documentation: coding-style: ask function-like macros to evaluate parameters Barry Song
2024-04-02 16:13 ` Jonathan Corbet
2024-04-02 21:21 ` Barry Song
2024-04-02 21:54 ` Joe Perches
2024-04-01 1:21 ` [PATCH v5 2/2] scripts: checkpatch: check unused parameters for function-like macro Barry Song
2024-04-01 2:37 ` Joe Perches [this message]
2024-04-02 0:16 ` Mac Xu
2024-04-02 1:39 ` Joe Perches
2024-04-02 15:05 ` Mac Xu
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=f5bb12d8602a03d28b2a8aeaffd8f74f001d692d.camel@perches.com \
--to=joe@perches.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=broonie@kernel.org \
--cc=charlemagnelasse@gmail.com \
--cc=chenhuacai@loongson.cn \
--cc=chris@zankel.net \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=jcmvbkbc@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lukas.bulwahn@gmail.com \
--cc=mac.xxn@outlook.com \
--cc=quic_jjohnson@quicinc.com \
--cc=sfr@canb.auug.org.au \
--cc=v-songbaohua@oppo.com \
--cc=workflows@vger.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
all inboxes | Powered by JetHome®