From: Nicolas Schier <n.schier@avm.de>
To: Julian Sun <sunjunchao2870@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, jack@suse.cz, brauner@kernel.org,
viro@zeniv.linux.org.uk, masahiroy@kernel.org, ojeda@kernel.org,
djwong@kernel.org, kvalo@kernel.org
Subject: Re: [PATCH] scripts: add macro_checker script to check unused parameters in macros
Date: Thu, 25 Jul 2024 06:48:12 +0200 [thread overview]
Message-ID: <20240725-interesting-annoying-mammoth-6bb3ef@buildd> (raw)
In-Reply-To: <CAHB1NagB0-N777xzODLe19YBV1UJn4YGuUo67-O9cgKKgc-CLg@mail.gmail.com>
On Wed, Jul 24, 2024 at 11:05:43PM -0400, Julian Sun wrote:
> Andrew Morton <akpm@linux-foundation.org> 于2024年7月24日周三 22:43写道:
> >
> > On Wed, 24 Jul 2024 22:30:49 -0400 Julian Sun <sunjunchao2870@gmail.com> wrote:
> >
> > > I noticed that you have already merged this patch into the
> > > mm-nonmm-unstable branch.
> >
> > Yup. If a patch looks desirable (and reasonably close to ready) I'll
> > grab it to give it some exposure and testing while it's under
> > development, To help things along and to hopefully arrive at a batter
> > end result.
> >
> > > If I want to continue refining this script,
> > > should I send a new v2 version or make modifications based on the
> > > current version?
> >
> >
> > > Either is OK - whatever makes most sense for the reviewers. Reissuing
> > > a large patch series for a single line change is counterproductive ;)
> Thanks for your clarification. I will send a new patch based on the
> current version.
Hi Julian,
can you please Cc linux-kbuild in v2?
Kind regards,
Nicolas
next prev parent reply other threads:[~2024-07-25 4:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 9:11 [PATCH] scripts: add macro_checker script to check unused parameters in macros Julian Sun
2024-07-23 22:09 ` Andrew Morton
2024-07-24 3:03 ` Julian Sun
2024-07-24 5:03 ` Andrew Morton
2024-07-24 9:06 ` Johannes Berg
2024-07-25 2:30 ` Julian Sun
2024-07-25 2:43 ` Andrew Morton
2024-07-25 3:05 ` Julian Sun
2024-07-25 4:48 ` Nicolas Schier [this message]
2024-07-25 8:00 ` Julian Sun
2024-07-24 10:00 ` Jan Kara
2024-07-25 2:12 ` Julian Sun
2024-07-24 13:30 ` Joe Perches
2024-07-25 2:09 ` Julian Sun
2024-07-25 3:40 ` Joe Perches
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=20240725-interesting-annoying-mammoth-6bb3ef@buildd \
--to=n.schier@avm.de \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=kvalo@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ojeda@kernel.org \
--cc=sunjunchao2870@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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