linux-kernel - Re: [PATCH] USB: add SPDX identifiers to all files in drivers/usb/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 21 Oct 2017 09:48:41 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Rob Herring <rob.herring@...aro.org>
Cc:     "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Kate Stewart <kstewart@...uxfoundation.org>,
        Philippe Ombredanne <pombredanne@...b.com>
Subject: Re: [PATCH] USB: add SPDX identifiers to all files in drivers/usb/

On Fri, Oct 20, 2017 at 10:26:22AM -0500, Rob Herring wrote:
> On Thu, Oct 19, 2017 at 3:38 AM, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> > It's good to have SPDX identifiers in all files to make it easier to
> > audit the kernel tree for correct licenses.  This patch adds these
> > identifiers to all files in drivers/usb/ based on a script and data from
> > Thomas Gleixner, Philippe Ombredanne, and Kate Stewart.
> >
> > Cc: Thomas Gleixner <tglx@...utronix.de>
> > Cc: Kate Stewart <kstewart@...uxfoundation.org>
> > Cc: Philippe Ombredanne <pombredanne@...b.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> > ---
> > Unless someone really complains, I'm going to add this to my tree for
> > 4.15-rc1.
> 
> Glad to see this. I've been suggesting folks use SPDX tags on dts
> files as those are often dual licensed, so we have lots of license
> boilerplate. But I've had some push back[1] but it's not something I
> care to spend cycles on. It would be good to have some statement on
> the use of tags. Anything new should use them (I can dust off my
> checkpatch.pl check for this)? This is a good task for newbies? It's
> each maintainer's decision? It's the copyright holder's (and their
> lawyer's) decision?

As for what type of a task this is, we have a script and a huge database
that has been worked on by some people to make a lot of this pretty
"automatic" to apply.

For the "odd" issues that Russell is worried about, those we can take as
a case-by-case basis after we get through all of the obvious ones first.

Thomas and I are going to talk about this next week in Prague to see if
we can come up with a plan...

thanks,

greg k-h