From: Joe Perches <joe@perches.com>
To: Charlemagne Lasse <charlemagnelasse@gmail.com>,
Barry Song <21cnbao@gmail.com>, Jonathan Corbet <corbet@lwn.net>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
Andy Whitcroft <apw@canonical.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
lukas.bulwahn@gmail.com
Cc: LKML <linux-kernel@vger.kernel.org>,
Xining Xu <ma.xxn@outlook.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v3 2/2] scripts: checkpatch: check unused parameters for function-like macro
Date: Fri, 29 Mar 2024 19:49:13 -0700 [thread overview]
Message-ID: <58ca38fdae3f702ed4f2982572f614ef7e3e8df8.camel@perches.com> (raw)
In-Reply-To: <CAFGhKbz70E3vihRkG4Hi20Tw8i7mGp=Z6j+NnELDTJd9cj9+Aw@mail.gmail.com>
On Sat, 2024-03-30 at 00:08 +0100, Charlemagne Lasse wrote:
> Hi,
>
> Can this patch please be dropped from Linux-next (currently via
> git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm#mm-everything)?
> It is obviously wrong when dealing with named variadic macro
> parameters:
I agree it was a bit early to add to -mm but
there is a fix for (most of) that coming up.
next prev parent reply other threads:[~2024-03-30 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 23:08 [PATCH v3 2/2] scripts: checkpatch: check unused parameters for function-like macro Charlemagne Lasse
2024-03-30 2:49 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-22 8:49 [PATCH v3 0/2] codingstyle: avoid unused parameters for a " Barry Song
2024-03-22 8:49 ` [PATCH v3 2/2] scripts: checkpatch: Check unused parameters for " 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=58ca38fdae3f702ed4f2982572f614ef7e3e8df8.camel@perches.com \
--to=joe@perches.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=charlemagnelasse@gmail.com \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=ma.xxn@outlook.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).