From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Cédric Le Goater" <clg@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH v2 6/7] scripts/checkpatch: use new hook for MAINTAINERS update check
Date: Wed, 14 May 2025 12:56:38 +0100 [thread overview]
Message-ID: <aCSE9uGxFqnrrVSu@redhat.com> (raw)
In-Reply-To: <c0e68194-6aa4-4ca8-bee3-ebd67cd96489@redhat.com>
On Wed, May 14, 2025 at 01:51:52PM +0200, Cédric Le Goater wrote:
> On 5/12/25 20:24, Daniel P. Berrangé wrote:
> > From: Daniel P. Berrangé <berrange@redhat.com>
> >
> > When seeing a new/deleted/renamed file we check to see if MAINTAINERS
> > is updated, but we don't give the user a list of files affected, as
> > we don't want to repeat the same warning many times over.
> >
> > Using the new file list hook, we can give a single warning at the
> > end with a list of filenames included.
> >
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > scripts/checkpatch.pl | 37 +++++++++++++++++++------------------
> > 1 file changed, 19 insertions(+), 18 deletions(-)
> >
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > index 4a18daa384..d416a6dcf9 100755
> > --- a/scripts/checkpatch.pl
> > +++ b/scripts/checkpatch.pl
> > @@ -1442,6 +1442,25 @@ sub process_file_list {
> > join("\n ", @acpi_nontestexpected) .
> > "\n\nfound in the same patch\n");
> > }
> > +
> > + my $sawmaintainers = 0;
> > + my @maybemaintainers;
> > + foreach my $fileinfo (@fileinfos) {
> > + if ($fileinfo->{action} ne "modified" &&
> > + $fileinfo->{filenew} !~ m#^tests/data/acpi/#) {
> > + push @maybemaintainers, $fileinfo->{filenew};
> > + }
> > + if ($fileinfo->{filenew} eq "MAINTAINEfRS") {
>
> MAINTAINEfRS ? looks like a typo.
Opps, an intentional typo when I was testing logic that
I accidentally committed.
>
>
> With that fixed,
>
>
> Reviewed-by: Cédric Le Goater <clg@redhat.com>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-05-14 11:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 18:24 [PATCH v2 0/7] scripts/checkpatch: refactor & fix SPDX-License-Identifier detection Daniel P. Berrangé
2025-05-12 18:24 ` [PATCH v2 1/7] Revert "scripts: mandate that new files have SPDX-License-Identifier" Daniel P. Berrangé
2025-05-14 11:43 ` Cédric Le Goater
2025-05-12 18:24 ` [PATCH v2 2/7] scripts/checkpatch.pl: fix various indentation mistakes Daniel P. Berrangé
2025-05-14 11:51 ` Cédric Le Goater
2025-05-12 18:24 ` [PATCH v2 3/7] scripts/checkpatch: introduce tracking of file start/end Daniel P. Berrangé
2025-05-14 11:54 ` Cédric Le Goater
2025-05-12 18:24 ` [PATCH v2 4/7] scripts/checkpatch: use new hook for ACPI test data check Daniel P. Berrangé
2025-05-12 18:24 ` [PATCH v2 5/7] scripts/checkpatch: use new hook for file permissions check Daniel P. Berrangé
2025-05-14 11:52 ` Cédric Le Goater
2025-05-12 18:24 ` [PATCH v2 6/7] scripts/checkpatch: use new hook for MAINTAINERS update check Daniel P. Berrangé
2025-05-14 11:51 ` Cédric Le Goater
2025-05-14 11:56 ` Daniel P. Berrangé [this message]
2025-05-12 18:24 ` [PATCH v2 7/7] scripts/checkpatch: reimplement mandate for SPDX-License-Identifier Daniel P. Berrangé
2025-05-13 18:32 ` Cédric Le Goater
2025-05-15 11:10 ` Daniel P. Berrangé
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=aCSE9uGxFqnrrVSu@redhat.com \
--to=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.