workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Barry Song <21cnbao@gmail.com>
Cc: akpm@linux-foundation.org, apw@canonical.com, broonie@kernel.org,
	 charlemagnelasse@gmail.com, chenhuacai@loongson.cn,
	chris@zankel.net,  corbet@lwn.net, dwaipayanray1@gmail.com,
	herbert@gondor.apana.org.au,  jcmvbkbc@gmail.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux@roeck-us.net, lukas.bulwahn@gmail.com,
	mac.xxn@outlook.com,  quic_jjohnson@quicinc.com,
	sfr@canb.auug.org.au, v-songbaohua@oppo.com,
	 workflows@vger.kernel.org
Subject: Re: [PATCH RESEND v6 2/2] scripts: checkpatch: check unused parameters for function-like macro
Date: Mon, 06 May 2024 09:11:35 -0700	[thread overview]
Message-ID: <0e0cf5fc8c78fac42f4c657421d16456a7adca7f.camel@perches.com> (raw)
In-Reply-To: <20240506071657.13434-1-21cnbao@gmail.com>

On Mon, 2024-05-06 at 19:16 +1200, 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
> > []
> > > @@ -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");
> > 
> > trivia:  This should be aligned to the open parenthesis.
> > 
> 
> Hi Joe,
> I assume you mean the below?
> 
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 9895d7e38a9f..2b812210b412 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -6044,7 +6044,7 @@ sub process {
>  # 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");
> +					     "Argument '$arg' is not used in function-like macro\n" . "$herectx");
>  				}
>  			}
> > Otherwise:
> > Acked-by: Joe Perches <joe@perches.com>

Yes, but please send a v7 instead of a separate patch
to akpm or perhaps Andrew could combine them or fix it
when applying v6


      reply	other threads:[~2024-05-06 16:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  1:46 [PATCH RESEND v6 0/2] codingstyle: avoid unused parameters for a " Barry Song
2024-05-06  1:46 ` [PATCH RESEND v6 1/2] Documentation: coding-style: ask function-like macros to evaluate parameters Barry Song
2024-05-06  1:46 ` [PATCH RESEND v6 2/2] scripts: checkpatch: check unused parameters for function-like macro Barry Song
2024-05-06  5:33   ` Joe Perches
2024-05-06  7:16     ` Barry Song
2024-05-06 16:11       ` Joe Perches [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=0e0cf5fc8c78fac42f4c657421d16456a7adca7f.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