linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: linux-edac@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-efi@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	james.morse@arm.com, rjw@rjwysocki.net,
	Tony Luck <tony.luck@intel.com>,
	linuxarm@huawei.com, ard.biesheuvel@linaro.org,
	nariman.poushin@linaro.org, Jon Masters <jcm@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	peter.maydell@linaro.org, linux-spdx@vger.kernel.org,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 0/6 V2] CCIX Protocol error reporting.
Date: Tue, 27 Aug 2019 15:44:47 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1908271539590.1939@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190820144732.2370-1-Jonathan.Cameron@huawei.com>

[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]

Jonathan,

On Tue, 20 Aug 2019, Jonathan Cameron wrote:

Cc+ linux-spdx@vger.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

      parent reply	other threads:[~2019-08-27 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 14:47 [PATCH 0/6 V2] CCIX Protocol error reporting Jonathan Cameron
2019-08-20 14:47 ` [PATCH 1/6 V2] efi / ras: CCIX Memory " Jonathan Cameron
2019-08-20 14:47 ` [PATCH 2/6 V2] efi / ras: CCIX Cache " Jonathan Cameron
2019-08-20 14:47 ` [PATCH 3/6 V2] efi / ras: CCIX Address Translation " Jonathan Cameron
2019-08-20 14:47 ` [PATCH 4/6 V2] efi / ras: CCIX Port " Jonathan Cameron
2019-08-20 14:47 ` [PATCH 5/6 V2] efi / ras: CCIX Link " Jonathan Cameron
2019-08-20 14:47 ` [PATCH 6/6 V2] efi / ras: CCIX Agent internal " Jonathan Cameron
2019-08-27 13:44 ` Thomas Gleixner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.1908271539590.1939@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bp@alien8.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=james.morse@arm.com \
    --cc=jcm@redhat.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mchehab@kernel.org \
    --cc=nariman.poushin@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=rjw@rjwysocki.net \
    --cc=tony.luck@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).