workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Mac Xu <mac.xxn@outlook.com>, Barry Song <21cnbao@gmail.com>,
	 "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"workflows@vger.kernel.org" <workflows@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>,
	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: Mon, 01 Apr 2024 18:39:16 -0700	[thread overview]
Message-ID: <3ea68e8fc46332d45e2af0d8de938628445b6691.camel@perches.com> (raw)
In-Reply-To: <MN0PR20MB471708D419907FFAF1DB0FC2F33E2@MN0PR20MB4717.namprd20.prod.outlook.com>

On Tue, 2024-04-02 at 00:16 +0000, Mac Xu wrote:
> > 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
> 
> Hi Joe,
> 
> Thank you for the comments, here's the code:
> 
> +# 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");
> +}
> 
> and here's the document for it which is inserted into the "Macros, Attributes and
> Symbols" section of checkpatch.rst starting from line 909:
> +
> +  **MACRO_ARG_UNUSED**
> +    If function-like macros do not utilize a parameter, it might result
> +    in a build warning. We advocate for utilizing static inline functions
> +    to replace such macros.
> +    For example, for a macro as below::
> +
> +      #define test(a) do { } while (0)
> +
> +    there would be a warning as below::
> +
> +      WARNING: Parameter 'a' is not used in function-like macro, please use
> +      static inline instead.
> 
> Please let me know if the document needs further re-wording to make it helpful enough
> to the readers.

Hi again Xining.

Thanks.

That looks good but it doesn't match the script output
which doesn't use ", please use static inline instead."
(and I believe the script should not output that too)

Another good thing would be to add a line like:

	See: https://www.kernel.org/doc/html/latest/process/coding-style.html#macros-enums-and-rtl

For example, from: checkpatch.rst

  **ALLOC_SIZEOF_STRUCT**
    The allocation style is bad.  In general for family of
    allocation functions using sizeof() to get memory size,
    constructs like::

      p = alloc(sizeof(struct foo), ...)

    should be::

      p = alloc(sizeof(*p), ...)

    See: https://www.kernel.org/doc/html/latest/process/coding-style.html#allocating-memory


  reply	other threads:[~2024-04-02  1:39 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
2024-04-02  0:16     ` Mac Xu
2024-04-02  1:39       ` Joe Perches [this message]
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=3ea68e8fc46332d45e2af0d8de938628445b6691.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