linux-kernel - Re: [PATCH v2 6/7] vmw_balloon: update copyright message

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 for Android: free password hash cracker in your pocket

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

Message-ID: <5151EA1B-D065-44D1-995C-47B791F574E1@vmware.com>
Date:   Fri, 15 Jun 2018 20:38:57 +0000
From:   Nadav Amit <namit@...are.com>
To:     "valdis.kletnieks@...edu" <valdis.kletnieks@...edu>
CC:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Xavier Deguillard <xdeguillard@...are.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v2 6/7] vmw_balloon: update copyright message

at 1:35 PM, valdis.kletnieks@...edu wrote:

> On Thu, 14 Jun 2018 05:33:46 -0000, Nadav Amit said:
> 
>>>> In addition, updating the year and adding a license tag.
> 
>>>> +// SPDX-License-Identifier: GPL-2.0
> 
>>> You still have a lot of boiler-plate text in here that can be removed.
>>> Please do so.
> 
>> But what else do you want me to remove? This is a standard GPL license. If I
>> am required to remove the GPL license, I will have to run checks to ensure
>> it is appropriate.
> 
> You mean the checks that you should have done when you stuck the SPDX
> tag on the file?
> 
> (Hint: Think of the SPDX tag as a '#include gplv2.license.blurb" :)

I matched the SPDX to the license we have, tut I don’t know whether my
company regards an SPDX tag as a sufficient means to protect copyrights,
which allows to remove all the rest of the text.

Just trying not to get fired for a stupid reason ;)