From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Philippe Ombredanne <pombredanne@nexb.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
Greg KH <gregkh@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Hans Verkuil <hans.verkuil@cisco.com>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [patch V2 7/7] scripts: Add SPDX checker script
Date: Tue, 28 Aug 2018 11:19:31 +0200 [thread overview]
Message-ID: <CAMuHMdVfFm8-vySaYBPt5J3f_RZcGHDhH+KFyadt=AhikzKaBQ@mail.gmail.com> (raw)
In-Reply-To: <CAOFm3uGECug6Hr8_UJt5QTGd_=Fae_Hvm_1Y9xyJri008EoHEQ@mail.gmail.com>
On Mon, May 14, 2018 at 4:38 PM Philippe Ombredanne
<pombredanne@nexb.com> wrote:
> On Wed, Apr 25, 2018 at 10:30 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > The SPDX-License-Identifiers are growing in the kernel and so grow
> > expression failures and license IDs are used which have no corresponding
> > license text file in the LICENSES directory.
> >
> > Add a script which gathers information from the LICENSES directory,
> > i.e. the various tags in the licenses and exception files and then scans
> > either input from stdin, which it treats as a single file or if started
> > without arguments it scans the full kernel tree.
> >
> > It checks whether the license expression syntax is correct and also
> > validates whether the license identifiers used in the expressions are
> > available in the LICENSES files.
>
> Looking good to me! And the use of ply is sleek.
For the record (currently Google doesn't find this issue yet):
ImportError: No module named ply
$ sudo apt-get install python-ply
ImportError: No module named git
$ sudo apt-get install python-git
Works!
Apparently I didn't have any of these two packages installed on any of my
Ubuntu 18.04LTS and 16.04LTS machines...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2018-08-28 9:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 20:30 [patch V2 0/7] LICENSES: Add missing License Text and provide a checker script Thomas Gleixner
2018-04-25 20:30 ` [patch V2 1/7] LICENSES/GPL2.0: Add GPL-2.0-only/or-later as valid identifiers Thomas Gleixner
2018-04-26 7:00 ` Greg Kroah-Hartman
2018-04-26 9:52 ` Mauro Carvalho Chehab
2018-04-25 20:30 ` [patch V2 2/7] LICENSES: Add X11 license Thomas Gleixner
2018-04-26 7:00 ` Greg Kroah-Hartman
2018-04-25 20:30 ` [patch V2 3/7] LICENSES: Add Apache 2.0 license text Thomas Gleixner
2018-04-26 7:00 ` Greg Kroah-Hartman
2018-04-26 14:30 ` Kate Stewart
2018-04-25 20:30 ` [patch V2 4/7] LICENSES: Add CDDL-1.0 " Thomas Gleixner
2018-04-26 7:01 ` Greg Kroah-Hartman
2018-04-26 14:29 ` Kate Stewart
2018-04-25 20:30 ` [patch V2 5/7] LICENSES: Add CC-BY-SA-4.0 " Thomas Gleixner
2018-04-26 7:01 ` Greg Kroah-Hartman
2018-04-26 14:27 ` Kate Stewart
2018-04-25 20:30 ` [patch V2 6/7] LICENSES: Add Linux-OpenIB " Thomas Gleixner
2018-04-26 7:01 ` Greg Kroah-Hartman
2018-04-26 14:24 ` Kate Stewart
2018-04-25 20:30 ` [patch V2 7/7] scripts: Add SPDX checker script Thomas Gleixner
2018-04-26 7:02 ` Greg Kroah-Hartman
2018-04-26 13:54 ` [patch V3 " Thomas Gleixner
2018-04-26 17:04 ` Greg Kroah-Hartman
2018-04-26 18:43 ` Thomas Gleixner
2018-05-14 14:35 ` [patch V2 " Philippe Ombredanne
2018-08-28 9:19 ` Geert Uytterhoeven [this message]
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='CAMuHMdVfFm8-vySaYBPt5J3f_RZcGHDhH+KFyadt=AhikzKaBQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hans.verkuil@cisco.com \
--cc=hch@lst.de \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=pombredanne@nexb.com \
--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;
as well as URLs for NNTP newsgroup(s).