From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Cédric Le Goater" <clg@kaod.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH v5 0/9] scripts/checkpatch: fix SPDX-License-Identifier detection
Date: Mon, 19 May 2025 18:09:55 +0100 [thread overview]
Message-ID: <20250519171004.352636-1-berrange@redhat.com> (raw)
This is hugely expanded an update of
https://lists.nongnu.org/archive/html/qemu-devel/2025-05/msg02040.html
In that series, Peter suggested creating standalone methods to act
as hooks to call when detecting the start/end of a file in a diff.
This implements that idea and adapts a number of existing checks
to use the new hooks.
Changed in v5:
- Actually make boilerplate text regex work, the '/x'
operator culls *all* whitespace from the regex, which
was not desirable as we need space between words.
- Fix inverted check of boilerplate result
Changed in v4:
- Pull our boilerplate match regex to separate variable
- Mention that SPDX is sufficient when reporting redundant
boilerplate
- Tweak commit message to explain indent changes better
Changed in v3:
- Add check for redundent license boilerplate text
- Fix check for Makefile names
Daniel P. Berrangé (9):
Revert "scripts: mandate that new files have SPDX-License-Identifier"
scripts/checkpatch.pl: fix various indentation mistakes
scripts/checkpatch: introduce tracking of file start/end
scripts/checkpatch: use new hook for ACPI test data check
scripts/checkpatch: use new hook for file permissions check
scripts/checkpatch: expand pattern for matching makefiles
scripts/checkpatch: use new hook for MAINTAINERS update check
scripts/checkpatch: reimplement mandate for SPDX-License-Identifier
scripts/checkpatch: reject license boilerplate on new files
scripts/checkpatch.pl | 389 +++++++++++++++++++++++++++---------------
1 file changed, 251 insertions(+), 138 deletions(-)
--
2.49.0
next reply other threads:[~2025-05-19 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 17:09 Daniel P. Berrangé [this message]
2025-05-19 17:09 ` [PATCH v5 1/9] Revert "scripts: mandate that new files have SPDX-License-Identifier" Daniel P. Berrangé
2025-05-19 17:09 ` [PATCH v5 2/9] scripts/checkpatch.pl: fix various indentation mistakes Daniel P. Berrangé
2025-05-19 17:09 ` [PATCH v5 3/9] scripts/checkpatch: introduce tracking of file start/end Daniel P. Berrangé
2025-05-19 17:09 ` [PATCH v5 4/9] scripts/checkpatch: use new hook for ACPI test data check Daniel P. Berrangé
2025-05-19 17:10 ` [PATCH v5 5/9] scripts/checkpatch: use new hook for file permissions check Daniel P. Berrangé
2025-05-19 17:10 ` [PATCH v5 6/9] scripts/checkpatch: expand pattern for matching makefiles Daniel P. Berrangé
2025-05-19 17:10 ` [PATCH v5 7/9] scripts/checkpatch: use new hook for MAINTAINERS update check Daniel P. Berrangé
2025-05-19 17:10 ` [PATCH v5 8/9] scripts/checkpatch: reimplement mandate for SPDX-License-Identifier Daniel P. Berrangé
2025-05-19 17:10 ` [PATCH v5 9/9] scripts/checkpatch: reject license boilerplate on new files Daniel P. Berrangé
2025-05-19 17:24 ` Peter Maydell
2025-05-19 17:25 ` Cédric Le Goater
2025-05-21 9:05 ` [PATCH v5 10/9] scripts/checkpatch.pl: mandate SPDX tag for Rust src files Daniel P. Berrangé
2025-05-21 17:18 ` Manos Pitsidianakis
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=20250519171004.352636-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=clg@kaod.org \
--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 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 NNTP newsgroup(s).