From: Thomas Huth <thuth@redhat.com>
To: Alexandru Elisei <alexandru.elisei@arm.com>,
pbonzini@redhat.com, drjones@redhat.com,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Cc: suzuki.poulose@arm.com, mark.rutland@arm.com
Subject: Re: [kvm-unit-tests] Adding the QCBOR library to kvm-unit-tests
Date: Tue, 15 Mar 2022 15:21:39 +0100 [thread overview]
Message-ID: <b1d5e4b7-c07c-0e34-ef6d-58aab19a41b2@redhat.com> (raw)
In-Reply-To: <YjCVxT1yo0hi6Vdc@monolith.localdoman>
On 15/03/2022 14.33, Alexandru Elisei wrote:
> Hi,
>
> Arm is planning to upstream tests that are being developed as part of the
> Confidential Compute Architecture [1]. Some of the tests target the
> attestation part of creating and managing a confidential compute VM, which
> requires the manipulation of messages in the Concise Binary Object
> Representation (CBOR) format [2].
>
> I would like to ask if it would be acceptable from a license perspective to
> include the QCBOR library [3] into kvm-unit-tests, which will be used for
> encoding and decoding of CBOR messages.
>
> The library is licensed under the 3-Clause BSD license, which is compatible
> with GPLv2 [4]. Some of the files that were created inside Qualcomm before
> the library was open-sourced have a slightly modified 3-Clause BSD license,
> where a NON-INFRINGMENT clause is added to the disclaimer:
>
> "THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
> WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
> MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE **AND NON-INFRINGEMENT**
> ARE DISCLAIMED" (emphasis by me on the added clause).
>
> The files in question include the core files that implement the
> encode/decode functionality, and thus would have to be included in
> kvm-unit-tests. I believe that the above modification does not affect the
> compatibility with GPLv2.
IANAL, but I think it should be ok to add those files to the kvm-unit-tests.
With regards to the "non-infringement" extension, it seems to be the one
mentioned here: https://enterprise.dejacode.com/licenses/public/bsd-x11/ ...
and on the "license condition" tab they mention that it is compatible with
the GPL. On gnu.org, they list e.g. the
https://www.gnu.org/licenses/license-list.html#X11License which also
contains a "non-infringement" statement, so that should really be compatible.
Thomas
next prev parent reply other threads:[~2022-03-15 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 13:33 [kvm-unit-tests] Adding the QCBOR library to kvm-unit-tests Alexandru Elisei
2022-03-15 14:21 ` Thomas Huth [this message]
2022-03-15 15:48 ` Alexandru Elisei
2022-03-15 15:25 ` Andrew Jones
2022-03-16 10:42 ` Alexandru Elisei
2022-03-16 10:44 ` Suzuki Kuruppassery Poulose
2022-03-16 10:51 ` Andrew Jones
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=b1d5e4b7-c07c-0e34-ef6d-58aab19a41b2@redhat.com \
--to=thuth@redhat.com \
--cc=alexandru.elisei@arm.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=mark.rutland@arm.com \
--cc=pbonzini@redhat.com \
--cc=suzuki.poulose@arm.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