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] [day] [month] [year] [list]
Message-ID: <bd4fc14d-ce63-93d5-6f52-7a1def7c57c3@ti.com>
Date:   Thu, 19 Dec 2019 21:30:31 -0600
From:   Suman Anna <s-anna@...com>
To:     Tero Kristo <t-kristo@...com>,
        Bjorn Andersson <bjorn.andersson@...aro.org>
CC:     <ohad@...ery.com>, <linux-remoteproc@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-omap@...r.kernel.org>
Subject: Re: [PATCH 02/17] remoteproc/omap: Switch to SPDX license identifiers

On 11/12/19 2:16 AM, Tero Kristo wrote:
> On 09/11/2019 03:03, Bjorn Andersson wrote:
>> On Mon 28 Oct 05:42 PDT 2019, Tero Kristo wrote:
>>
>>> From: Suman Anna <s-anna@...com>
>>>
>>> Use the appropriate SPDX license identifiers in various OMAP remoteproc
>>> source files and drop the previous boilerplate license text.
>>>
>>> Signed-off-by: Suman Anna <s-anna@...com>
>>> Signed-off-by: Tero Kristo <t-kristo@...com>
>>> ---
>>>   drivers/remoteproc/omap_remoteproc.h | 27 +--------------------------
>>>   1 file changed, 1 insertion(+), 26 deletions(-)
>>>
>>> diff --git a/drivers/remoteproc/omap_remoteproc.h
>>> b/drivers/remoteproc/omap_remoteproc.h
>>> index f6d2036d383d..1e6fef753c4f 100644
>>> --- a/drivers/remoteproc/omap_remoteproc.h
>>> +++ b/drivers/remoteproc/omap_remoteproc.h
>>> @@ -1,35 +1,10 @@
>>> +/* SPDX-License-Identifier: (GPL-2.0 OR BSD-3-Clause) */
>>
>> Please confirm that you actually intend to change the license from BSD
>> to dual here.
> 
> That is a very good point. Let me try to get clarification to this
> internally, this series is anyways too late for 5.5 so there is no rush
> to get this done anytime soon. Worst case I just drop this patch and
> keep the existing license in place.

He he, even I can't seem to recall the reason why I used dual here.
Let's stick with BSD-3-Clause which is the original license text below.

regards
Suman

> 
> -Tero
> 
>>
>> Regards,
>> Bjorn
>>
>>>   /*
>>>    * Remote processor messaging
>>>    *
>>>    * Copyright (C) 2011 Texas Instruments, Inc.
>>>    * Copyright (C) 2011 Google, Inc.
>>>    * All rights reserved.
>>> - *
>>> - * Redistribution and use in source and binary forms, with or without
>>> - * modification, are permitted provided that the following conditions
>>> - * are met:
>>> - *
>>> - * * Redistributions of source code must retain the above copyright
>>> - *   notice, this list of conditions and the following disclaimer.
>>> - * * Redistributions in binary form must reproduce the above copyright
>>> - *   notice, this list of conditions and the following disclaimer in
>>> - *   the documentation and/or other materials provided with the
>>> - *   distribution.
>>> - * * Neither the name Texas Instruments nor the names of its
>>> - *   contributors may be used to endorse or promote products derived
>>> - *   from this software without specific prior written permission.
>>> - *
>>> - * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>>> - * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>>> - * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
>>> FOR
>>> - * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
>>> - * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
>>> INCIDENTAL,
>>> - * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
>>> - * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
>>> USE,
>>> - * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
>>> ANY
>>> - * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
>>> - * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
>>> USE
>>> - * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>>>    */
>>>     #ifndef _OMAP_RPMSG_H
>>> -- 
>>> 2.17.1
>>>
>>> -- 
> 
> -- 
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ