linux-kernel - Re: [PATCH 0/6 V2] CCIX Protocol error reporting.

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]

Date:   Tue, 27 Aug 2019 15:44:47 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Jonathan Cameron <Jonathan.Cameron@...wei.com>
cc:     linux-edac@...r.kernel.org, linux-acpi@...r.kernel.org,
        linux-efi@...r.kernel.org, Borislav Petkov <bp@...en8.de>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        james.morse@....com, rjw@...ysocki.net,
        Tony Luck <tony.luck@...el.com>, linuxarm@...wei.com,
        ard.biesheuvel@...aro.org, nariman.poushin@...aro.org,
        Jon Masters <jcm@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>, peter.maydell@...aro.org,
        linux-spdx@...r.kernel.org, Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 0/6 V2] CCIX Protocol error reporting.

Jonathan,

On Tue, 20 Aug 2019, Jonathan Cameron wrote:

Cc+ linux-spdx@...r.kernel.org

> The following boilerplate is granting rights to the kernel.
> Note that I haven't applied the CCIX copyright notice anywhere in this
> series because we aren't quoting from the specification.  That is
> much more likely to happen in documentation patches than in code.
> 
> Like anything else in this series it is open to comment.
> 
> This patch is being distributed by the CCIX Consortium, Inc. (CCIX) to
> you and other parties that are participating (the "participants") in the
> Linux kernel with the understanding that the participants will use CCIX's
> name and trademark only when this patch is used in association with the
> Linux kernel and associated user space.

The code is licensed under GPLV2, so what precludes any other GPLV2 project
to import that code?

If there is a mentioning of CCIX Consortium in the imported code then you
cannot impose that this needs to be removed because it ends up in something
which is neither Linux kernel nor associated user space. And that's
especially true when this ends up being a copyright notice.
 
> CCIX is also distributing this patch to these participants with the
> understanding that if any portion of the CCIX specification will be
> used or referenced in the Linux kernel, the participants will not modify
> the cited portion of the CCIX specification and will give CCIX proper
> copyright attribution by including the following copyright notice with
> the cited part of the CCIX specification:
> "© 2019 CCIX CONSORTIUM, INC. ALL RIGHTS RESERVED."

Just to prove the point.

Thanks,

	tglx