From: Mac Xu <mac.xxn@outlook.com>
To: Joe Perches <joe@perches.com>, Barry Song <21cnbao@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Cc: "apw@canonical.com" <apw@canonical.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"chenhuacai@loongson.cn" <chenhuacai@loongson.cn>,
"chris@zankel.net" <chris@zankel.net>,
"corbet@lwn.net" <corbet@lwn.net>,
"dwaipayanray1@gmail.com" <dwaipayanray1@gmail.com>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"lukas.bulwahn@gmail.com" <lukas.bulwahn@gmail.com>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"v-songbaohua@oppo.com" <v-songbaohua@oppo.com>,
"workflows@vger.kernel.org" <workflows@vger.kernel.org>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: [PATCH v4 2/2] scripts: checkpatch: check unused parameters for function-like macro
Date: Sun, 31 Mar 2024 23:21:44 +0000 [thread overview]
Message-ID: <MN0PR20MB471701E2FEB9DBCDCDCD9D44F3382@MN0PR20MB4717.namprd20.prod.outlook.com> (raw)
In-Reply-To: <dbe8ea1a6a3b599a00eeb8ba0254fde785a500b9.camel@perches.com>
> On Sun, 2024-03-31 at 13:46 +0000, Mac Xu wrote:
> > > On Thu, 2024-03-28 at 15: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.
> > > []
> > > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> >
> []
> > > It seems this logic is a bit redundant to existing
> > > code and might be better added in the block that starts
> > >
> > > (line 6026)
> > > # check if any macro arguments are reused (ignore '...' and 'type')
> > >
> > > as that already does each param in a #define and
> > > ignores ... and type
> >
> > Hi Joe,
> >
> > Thank you for your comments with insights, as you said, code block of line 6026 is a better place to
> > place this new logic, as it already handles the logic I'd wanted like extracting, splitting and trimming
> > the arguments, excluding the trailing comments etc.
> >
> > By placing the logic in the new place, code duplicates are reduced.
> >
> > Here's my new code (inserted from line 6044):
> > +# check if this is an unused argument
> > + if ($define_stmt !~ /\b$arg\b/) {
> > + WARN("UNUSED_ARG_IN_MACRO",
> Perhaps
> WARN("MACRO_ARG_UNUSED",
> ...
>
> to better match the others above it in the block:
>
> CHK("MACRO_ARG_REUSE",
> and
> CHK("MACRO_ARG_PRECEDENCE",
>
> Other than that trivial bit, seems ok.
Sure, updated, thank you!
+# 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");
+}
Regards,
Xining
next prev parent reply other threads:[~2024-03-31 23:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 2:21 [PATCH v4 0/2] codingstyle: avoid unused parameters for a " Barry Song
2024-03-28 2:21 ` [PATCH v4 1/2] Documentation: coding-style: ask function-like macros to evaluate parameters Barry Song
2024-03-28 2:21 ` [PATCH v4 2/2] scripts: checkpatch: check unused parameters for function-like macro Barry Song
2024-03-28 9:57 ` Joe Perches
2024-03-31 13:43 ` Mac Xu
2024-03-31 13:46 ` Mac Xu
2024-03-31 15:54 ` Joe Perches
2024-03-31 23:21 ` Mac Xu [this message]
2024-03-28 16:01 ` Jeff Johnson
2024-03-28 21:24 ` Barry Song
2024-03-28 4:22 ` [PATCH v4 0/2] codingstyle: avoid unused parameters for a " Barry Song
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=MN0PR20MB471701E2FEB9DBCDCDCD9D44F3382@MN0PR20MB4717.namprd20.prod.outlook.com \
--to=mac.xxn@outlook.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=broonie@kernel.org \
--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=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lukas.bulwahn@gmail.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