From: Joe Perches <joe@perches.com>
To: Rob Herring <robh@kernel.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Whitcroft <apw@canonical.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Philippe Ombredanne <pombredanne@nexb.com>
Subject: Re: [PATCH] checkpatch.pl: Add SPDX license tag check
Date: Thu, 01 Feb 2018 13:49:04 -0800 [thread overview]
Message-ID: <1517521744.7489.64.camel@perches.com> (raw)
In-Reply-To: <20180201211429.32696-1-robh@kernel.org>
On Thu, 2018-02-01 at 15:14 -0600, Rob Herring wrote:
> Add SPDX license tag check based on the rules defined in
> Documentation/process/license-rules.rst. To summarize, SPDX license tags
> should be on the 1st line (or 2nd line in scripts) using the appropriate
> comment style for the file type.
>
> Cc: Andy Whitcroft <apw@canonical.com>
> Cc: Joe Perches <joe@perches.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Philippe Ombredanne <pombredanne@nexb.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> I didn't get around to resending once license-rules.rst landed in -next.
> Hopefully, this can be picked up for 4.16 so folks can start using it.
> SPDX tags have already become a frequent review comment.
Seems sensible enough now.
Here are some other suggestions.
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -2866,6 +2869,30 @@ sub process {
> }
> }
>
> +# check for using SPDX license tag at beginning of files
> + if ($realline == $checklicenseline) {
> + if ($realfile =~ /\.(?:sh|pl|py)/ && $rawline =~ /\[ \+]\s*\!\#/) {
There are many files with a #! shebang that do
not use these filename types.
$ git grep -P --name-only '^\s*\#\!\s*/(?:bin|usr)' | \
grep -vP
"(?:txt|rst|py|sh|pl)$" | wc -l
158
i.e.: .tc and .awk files and ~100 files without extensions
So I would add awk and tc to the $realfile test and
perhaps extend this check to test if the file is not
binary and executable.
> + $checklicenseline = 2;
> + } elsif ($rawline =~ /^\+/) {
> + my $comment = "";
> + if ($realfile =~ /\.(h|s|S)$/) {
> + $comment = '/*';
> + } elsif ($realfile =~ /\.(c|dts|dtsi)$/) {
> + $comment = '//';
> + } elsif ($realfile =~ /\.(sh|pl|py)$/) {
> + $comment = '#';
> + } elsif ($realfile =~ /\.rst$/) {
> + $comment = '..';
> + }
> +
> + if ($comment !~ /^$/ &&
> + $rawline !~ /^\+\Q$comment\E SPDX-License-Identifier: /) {
> + WARN("SPDX_LICENSE_TAG",
> + "Missing or malformed SPDX-License-Identifier tag in 1st (or 2nd for scripts) line\n" . $herecurr);
Perhaps 'Missing ... in line $checklicense\n"
next prev parent reply other threads:[~2018-02-01 21:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 21:14 [PATCH] checkpatch.pl: Add SPDX license tag check Rob Herring
2018-02-01 21:49 ` Joe Perches [this message]
2018-02-02 7:56 ` Greg Kroah-Hartman
2018-02-08 14:23 ` Philippe Ombredanne
-- strict thread matches above, loose matches on Subject: below --
2017-11-09 1:10 Rob Herring
2017-11-09 2:10 ` Joe Perches
2017-11-09 9:12 ` Greg Kroah-Hartman
2017-11-09 13:55 ` Joe Perches
2017-11-09 13:47 ` Rob Herring
2017-11-09 15:39 ` Joe Perches
2017-11-09 18:12 ` Rob Herring
2017-11-09 18:27 ` 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=1517521744.7489.64.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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