From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Ira Weiny" <ira.weiny@intel.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Michael Tokarev" <mjt@tls.msk.ru>,
qemu-devel@nongnu.org, "Michael Tsirkin" <mst@redhat.com>,
"Fan Ni" <fan.ni@samsung.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
linuxarm@huawei.com,
"Yuquan Wang" <wangyuquan1236@phytium.com.cn>,
"Dave Jiang" <dave.jiang@intel.com>,
"Alison Schofield" <alison.schofield@intel.com>,
"Vishal Verma" <vishal.l.verma@intel.com>,
"Dan Williams" <dan.j.williams@intel.com>
Subject: Re: [PATCH 2/3] hw/mem/cxl_type3: Add missing copyright and license notice
Date: Tue, 19 Sep 2023 11:00:16 +0100 [thread overview]
Message-ID: <20230919110016.00007a9d@Huawei.com> (raw)
In-Reply-To: <ZQlgCgC1gHF9i7Ad@redhat.com>
On Tue, 19 Sep 2023 09:47:06 +0100
Daniel P. Berrangé <berrange@redhat.com> wrote:
> On Mon, Sep 18, 2023 at 02:14:40PM -0700, Ira Weiny wrote:
> > Jonathan Cameron wrote:
> > > On Mon, 18 Sep 2023 17:31:38 +0100
> > > Peter Maydell <peter.maydell@linaro.org> wrote:
> > >
> > > > On Mon, 18 Sept 2023 at 16:04, Jonathan Cameron
> > > > <Jonathan.Cameron@huawei.com> wrote:
> > > > >
> > > > > This has been missing from the start. Assume it should match
> > > > > with cxl/cxl-component-utils.c as both were part of early
> > > > > postings from Ben.
> > > >
> > > > Sounds plausible -- is there an Intel person who could give us
> > > > an acked-by for this?
> >
> > While we are at it; what about .../hw/mem/cxl_type3_stubs.c?
> >
> > > >
> > > > (Ideally we wouldn't have let more gpl-2-only code into the
> > > > codebase without a rationale...)
> >
> > I'm curious about this statement. Does the qemu project not want gpl v2
> > only code?
>
> Correct, this is explicitly stated in the LICENSE file:
>
> [quote]
> As of July 2013, contributions under version 2 of the GNU General Public
> License (and no later version) are only accepted for the following files
> or directories: bsd-user/, linux-user/, hw/vfio/, hw/xen/xen_pt*.
> [/quote]
>
> > I agree with Jonathan that this is the intention of Ben's
> > initial submission; so from that PoV.
>
> Ideally we would get all QEMU CXL contributors to agree to re-license
> to the GPL-2.0-or-later, unless the code has been copied from another
> project which was GPL-2.0-only thus forcing our code.
>
> >
> > Acked-by: Ira Weiny <ira.weiny@intel.com>
> >
> > Going forward I'd like to better understand the qemu communities view.
>
> Please follow the LICENSE file which is explicit about QEMU's views
> per the quoted text above.
I'd be fine with relaxing these, but there are quite a few contributors
so it will be a little difficult to establish.
Given, for that to be useful we need to do all the CXL files, I'll post
a v2 of this series setting this to GPL-v2-only and we can see if we
can address relicencing at a later date.
>
> With regards,
> Daniel
next prev parent reply other threads:[~2023-09-19 10:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 15:02 [PATCH 0/3] hw/cxl: Misc small fixes Jonathan Cameron via
2023-09-18 15:02 ` [PATCH 1/3] hw/cxl: Fix out of bound array access Jonathan Cameron via
2023-09-18 16:11 ` Fan Ni
2023-09-18 15:02 ` [PATCH 2/3] hw/mem/cxl_type3: Add missing copyright and license notice Jonathan Cameron via
2023-09-18 16:12 ` Fan Ni
2023-09-18 16:31 ` Peter Maydell
2023-09-18 17:00 ` Jonathan Cameron via
2023-09-18 17:26 ` Dave Jiang
2023-09-18 17:38 ` Peter Maydell
2023-09-19 9:35 ` Jonathan Cameron via
2023-09-18 18:17 ` Dave Jiang
2023-09-18 21:14 ` Ira Weiny
2023-09-19 8:47 ` Daniel P. Berrangé
2023-09-19 10:00 ` Jonathan Cameron via [this message]
2023-09-18 21:21 ` Warner Losh
2023-09-18 15:02 ` [PATCH 3/3] docs/cxl: Cleanout some more aarch64 examples Jonathan Cameron via
2023-09-18 16:13 ` Fan Ni
2023-09-18 16:35 ` Peter Maydell
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=20230919110016.00007a9d@Huawei.com \
--to=qemu-devel@nongnu.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=alison.schofield@intel.com \
--cc=berrange@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=fan.ni@samsung.com \
--cc=ira.weiny@intel.com \
--cc=linuxarm@huawei.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=vishal.l.verma@intel.com \
--cc=wangyuquan1236@phytium.com.cn \
/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).