workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Barry Song <21cnbao@gmail.com>,
	akpm@linux-foundation.org,  linux-doc@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, 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: Thu, 28 Mar 2024 02:57:35 -0700	[thread overview]
Message-ID: <ef2c96e40bcf777535c9ff2405e4dc5b3138b27e.camel@perches.com> (raw)
In-Reply-To: <20240328022136.5789-3-21cnbao@gmail.com>

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
[]
> @@ -6109,6 +6109,36 @@ sub process {
>  				WARN("TRAILING_SEMICOLON",
>  				     "macros should not use a trailing semicolon\n" . "$herectx");
>  			}
> +
> +			# match "\s*" rather than "\s+" after the balanced parens, as macro definition with arguments
> +			# is not required to have whitespace after arguments
> +			if ($dstat =~ /^\+\s*#\s*define\s+$Ident$balanced_parens\s*(\S+.*)(\/[\/*].*)?/) {

I think '(\/[\/*].*)?' doesn't do what you expect
perhaps '(\/[\/\*].*)?'
though I don't know why this should be capture group

> +				my $params = $1 || "";


> +				my $body = $2 || "";

Should never get the || "" as the 2nd capture group is not optional

> +
> +			    # get the individual params
> +				$params =~ tr/()//d;
> +				# remove leading and trailing whitespace
> +				$params =~ s/^\s+|\s+$//g;
> +
> +				$ctx =~ s/\n*$//;
> +				my $cnt = statement_rawlines($ctx);
> +				my $herectx = get_stat_here($linenr, $cnt, $here);
> +
> +				if ($params ne "") {

probably unnecessary

> +					my @paramList = split /,\s*/, $params;

please use split() with parentheses

> +					foreach my $param(@paramList) {

maybe
				foreach my $param (split(/,/, $params) {
					$param = trim($param);
					next if ($param =~ /\.\.\.$/);

> +						if ($param =~ /\.\.\.$/) {
> +							# if the param name ends with "...", skip the check
> +							next;
> +						}
> +						if ($body !~ /\b$param\b/) {
> +							WARN("UNUSED_PARAM_IN_MACRO",
> +								"Parameter '$param' is not used in function-like macro\n" . "$herectx");
> +						}
> +					}

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


  reply	other threads:[~2024-03-28  9:57 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 [this message]
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
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=ef2c96e40bcf777535c9ff2405e4dc5b3138b27e.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=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=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