linux-kernel - Re: [PATCH] samples: replace outdated permission statement with SPDX identifiers

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]

Message-ID: <20171117155353.02950038@lwn.net>
Date:   Fri, 17 Nov 2017 15:53:53 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Martin Kepplinger <martink@...teo.de>, akpm@...ux-foundation.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] samples: replace outdated permission statement with
 SPDX identifiers

On Thu, 16 Nov 2017 12:41:10 +0100
Greg KH <gregkh@...uxfoundation.org> wrote:

> > I'll fold this in, in the thread here. I guess this change is what Greg
> > had in mind? Or would you prefer having including SPDX and removing
> > permission statement seperately?  
> 
> I have been doing them in 2 steps, but only because the files I modified
> were in different "chunks" (i.e. add missing SPDX identifiers to a bunch
> of files in a directory, and then the second patch would remove the
> license identifiers for all files in that directory).  As that type of
> patch flow doesn't make sense here, I think what you did was just fine.

So I'll confess to being a little worried about removing the boilerplate:

	And it's important to notice that while adding a SPDX line should
	not really be controversial (as long as you get the license right,
	of course - Greg&co have the CSV files for everything, in case you
	want to check things you maintain), before removing the
	boiler-plate you really need to feel like you "own" the file.
	— Linus (https://lkml.org/lkml/2017/11/2/715)

Are we sure that we're not going to get in trouble with the people who do
"own" those files if we rip out the boilerplate?  It would be good to have
some clarity on when that can be done.

Thanks,

jon