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:   Mon, 27 Nov 2017 09:15:14 +0100
From:   Christian Borntraeger <borntraeger@...ibm.com>
To:     Heiko Carstens <heiko.carstens@...ibm.com>,
        "Michael S. Tsirkin" <mst@...hat.com>
Cc:     linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org,
        Thomas Huth <thuth@...hat.com>,
        Cornelia Huck <cohuck@...hat.com>,
        Halil Pasic <pasic@...ux.vnet.ibm.com>,
        Martin Schwidefsky <schwidefsky@...ibm.com>
Subject: Re: [PATCH v2 2/2] s390/virtio: add BSD license to virtio-ccw



On 11/24/2017 06:18 PM, Heiko Carstens wrote:
> On Fri, Nov 24, 2017 at 07:02:41PM +0200, Michael S. Tsirkin wrote:
>> On Fri, Nov 24, 2017 at 05:53:01PM +0100, Heiko Carstens wrote:
>>>>> Is there any reason to add the whole BSD 3 clause license text? I'd prefer
>>>>> if it would be just the simple new SPDX-License-Identifier above.
>>
>> I added  it for consistency with other virtio headers.
> 
> Well, one of the points of the SPDX tags is to avoid the countless
> duplication of license texts. Adding a license text is easy, removing it
> again later is not as easy. Therefore I would prefer to avoid the
> duplication here again.
> 
> Cornelia, Christian, any opinion here?

I would prefer to not have the full licence text and only have the SPDX string
if that is allowed by the licence.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ