From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/3] scripts: mandate that new files have SPDX-License-Identifier
Date: Mon, 7 Oct 2024 17:13:24 -0300 [thread overview]
Message-ID: <cc177f5e-123e-4c5d-9b6a-a3515a9bc863@linaro.org> (raw)
In-Reply-To: <20241007154548.1144961-2-berrange@redhat.com>
On 7/10/24 12:45, Daniel P. Berrangé wrote:
> Going forward we want all newly created source files to have an
> SPDX-License-Identifier tag present.
>
> Initially mandate this for C, Python and Perl source files, and
> encourage this for other file types.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> scripts/checkpatch.pl | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 1b21249c91..cc266abdcd 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -1378,6 +1378,8 @@ sub process {
> my $in_imported_file = 0;
> my $in_no_imported_file = 0;
> my $non_utf8_charset = 0;
> + my $expect_spdx = 0;
> + my $expect_spdx_file;
>
> our @report = ();
> our $cnt_lines = 0;
> @@ -1615,6 +1617,30 @@ sub process {
> WARN("added, moved or deleted file(s), does MAINTAINERS need updating?\n" . $herecurr);
> }
>
> +# All new files should have a SPDX-License-Identifier tag
> + if ($line =~ /^new file mode\s*\d+\s*$/) {
> + if ($expect_spdx) {
> + if ($expect_spdx_file =~ /\.(c|h|py|pl|c\.inc)$/) {
[ch]\.inc to also mandat for *.h.inc?
Otherwise, thanks!
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> + # source code files MUST have SPDX license declared
> + ERROR("expected 'SPDX-License-Identifer' in new file $expect_spdx_file");
> + } else {
> + # Other files MAY have SPDX license if appropriate
> + WARNING("Does new file $expect_spdx_file need 'SPDX-License-Identifer'?");
> + }
> + }
> + $expect_spdx = 1;
> + $expect_spdx_file = undef;
> + } elsif ($expect_spdx) {
> + $expect_spdx_file = $realfile unless defined $expect_spdx_file;
> +
> + # SPDX tagsd may occurr in comments which were
> + # stripped from '$line', so use '$rawline'
> + if ($rawline =~ /SPDX-License-Identifier/) {
> + $expect_spdx = 0;
> + $expect_spdx_file = undef;
> + }
> + }
> +
> # Check for wrappage within a valid hunk of the file
> if ($realcnt != 0 && $line !~ m{^(?:\+|-| |\\ No newline|$)}) {
> ERROR("patch seems to be corrupt (line wrapped?)\n" .
next prev parent reply other threads:[~2024-10-07 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 15:45 [PATCH 0/3] scripts: mandate use of SPDX-License-Identifier tags in new files Daniel P. Berrangé
2024-10-07 15:45 ` [PATCH 1/3] scripts: mandate that new files have SPDX-License-Identifier Daniel P. Berrangé
2024-10-07 16:12 ` Brian Cain
2024-10-07 20:13 ` Philippe Mathieu-Daudé [this message]
2024-10-07 15:45 ` [PATCH 2/3] scripts: validate SPDX license choices Daniel P. Berrangé
2024-10-07 16:19 ` Brian Cain
2024-10-07 16:49 ` Daniel P. Berrangé
2024-10-07 15:45 ` [PATCH 3/3] scripts: forbid use of arbitrary SPDX tags besides license identifiers Daniel P. Berrangé
2024-10-07 20:17 ` Philippe Mathieu-Daudé
2024-10-07 15:56 ` [PATCH 0/3] scripts: mandate use of SPDX-License-Identifier tags in new files Peter Maydell
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=cc177f5e-123e-4c5d-9b6a-a3515a9bc863@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--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).