From: Joe Perches <joe@perches.com>
To: jim.cromie@gmail.com
Cc: linux-kernel@vger.kernel.org, akpm@linuxfoundation.org,
Andy Whitcroft <apw@canonical.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH 1/1] checkpatch: allow multi-statement declarative macros.
Date: Thu, 16 May 2024 17:37:39 -0700 [thread overview]
Message-ID: <045de91c8b8e6c8ca60b2c4baf4430bd5cd5eeea.camel@perches.com> (raw)
In-Reply-To: <CAJfuBxxEgCT+4SVAxoWb1xvAqhgij489=z+FH9iuXwYksm-RWA@mail.gmail.com>
On Thu, 2024-05-16 at 09:20 -0600, jim.cromie@gmail.com wrote:
> On Thu, May 16, 2024 at 8:43 AM Joe Perches <joe@perches.com> wrote:
> >
> > On Thu, 2024-05-16 at 08:14 -0600, Jim Cromie wrote:
> > > Declarative macros, which declare/define storage (at either file or
> > > function scope), cannot be wrapped in do-while statements. So
> > > checkpatch advice is incorrect here.
> > >
> > > The code has an $exceptions regex which allows multiple statements
> > > based on the macro name, etc; /DECLARE_PER_CPU|DEFINE_PER_CPU/ are
> > > currently accepted, widen those to accept /DECLARE|DEFINE/.
> >
> > It seems this exempts too large a number of these macros
> >
> > $ git grep -P '^\s*\#\s*define\s+\w*(?:DECLARE|DEFINE)\w*'|wc -l
> > 5075
> >
>
> wow, thats more than Id have thought.
>
> > How about somehow limiting these exemptions more strictly?
>
> agreed. I'll just add my 1 exceptional macro name.
> resending shortly.
Is this macro used in a lot of places?
Otherwise, why not just ignore the macro where it occurs?
prev parent reply other threads:[~2024-05-17 0:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 14:14 [PATCH 1/1] checkpatch: allow multi-statement declarative macros Jim Cromie
2024-05-16 14:43 ` Joe Perches
2024-05-16 15:20 ` jim.cromie
2024-05-17 0:37 ` 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=045de91c8b8e6c8ca60b2c4baf4430bd5cd5eeea.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
/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