public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Laszlo Ersek <lersek@redhat.com>,
	Lars Kurth <lars.kurth@citrix.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
	"Jordan Justen" <jordan.l.justen@intel.com>,
	"Anthony Perard" <anthony.perard@citrix.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Stefan Berger" <stefanb@linux.ibm.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>
Subject: Re: PATCH] Change EDK II to BSD+Patent License
Date: Wed, 20 Mar 2019 18:42:47 +0000	[thread overview]
Message-ID: <de78bacc-1b4c-c703-c5b0-6ddfd531c5aa@arm.com> (raw)
In-Reply-To: <2439277a-b103-50d4-4de2-f1d3e17c53a3@redhat.com>

Hi,

On 20/03/2019 18:25, Laszlo Ersek wrote:
> On 03/20/19 14:03, Lars Kurth wrote:
>> On 15/03/2019, 17:48, "Lars Kurth" <lars.kurth@citrix.com> wrote:
>>      On 15/03/2019, 10:18, "Julien Grall" <julien.grall@arm.com> wrote:
>> Is the issue that you don’t trust that the license specified in the files are correct?
> 
> No -- the question is whether the license included in the files
> mentioned is indeed the MIT license, suitable for a replacement with the
> appropriate SPDX license ID.
> 
>>
>>      > (2.2.2) Files that seem to be covered by the MIT license.
>>      >
>>      >            OvmfPkg/Include/IndustryStandard/Xen/arch-arm/xen.h
>>
>> I can't identify where in the Xen tree this file came from. There is no corresponding xen.h file in the Xen tree at [xen.git] / xen / include / public / arch-arm /
>> @Julien, @Anthony: can you clarify
> 
> This file was first added to edk2 in b94c3ac93d57 ("Ovmf/Xen: implement
> XenHypercallLib for ARM", 2015-02-28).

It is a copy of public/arch-arm.h. Somehow all the other projects created the 
file under arch-arm/xen.h.

> 
> https://github.com/tianocore/edk2/commit/b94c3ac93d57
> 
> And from the Xen project (I think), it was Reviewed-by: Stefano
> Stabellini <stefano.stabellini@eu.citrix.com>. (I vaguely recall that
> Stefano's emai has changed since.)

That's correct. He is working for Xilinx now.

> 
>>
>>      >            OvmfPkg/Include/IndustryStandard/Xen/arch-x86/xen-x86_32.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/arch-x86/xen-x86_64.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/arch-x86/xen.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/event_channel.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/grant_table.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/hvm/hvm_op.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/hvm/params.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/io/blkif.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/io/console.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/io/protocols.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/io/ring.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/io/xenbus.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/io/xs_wire.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/memory.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/xen-compat.h
>>      >            OvmfPkg/Include/IndustryStandard/Xen/xen.h
>>
>> These all appear to originate from [xen.git] / xen / include / public
>> In the Xen tree these all have explicit MIT licenses, which implies that the license headers are indeed correct.
> 
> Thanks -- so can we replace the license blocks with
> 
>    SPDX-License-Identifier: MIT
> 
> ? (See e.g. <https://spdx.org/ids-how>.)

I spoke with Lars today, this identifier would be suitable for the headers.

Cheers,

-- 
Julien Grall


  reply	other threads:[~2019-03-20 18:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 17:54 PATCH] Change EDK II to BSD+Patent License Kinney, Michael D
2019-03-14 10:55 ` Laszlo Ersek
2019-03-14 19:06   ` Julien Grall
     [not found]     ` <8F40F2BF-B40F-4338-A832-70AE84B26408@citrix.com>
2019-03-15  9:35       ` Julien Grall
     [not found]         ` <6FBC013D-4BC9-454C-9D4D-87C96F435704@citrix.com>
2019-03-15 17:18           ` Julien Grall
     [not found]             ` <C2A0176C-8197-421A-9CA9-2B416DF17EAB@citrix.com>
2019-03-20 12:09               ` Laszlo Ersek
2019-03-23  0:44                 ` Kinney, Michael D
2019-03-25 10:04                   ` Laszlo Ersek
     [not found]               ` <720E0EE9-2AED-4110-827D-B87DE5F52862@citrix.com>
2019-03-20 18:25                 ` Laszlo Ersek
2019-03-20 18:42                   ` Julien Grall [this message]
2019-03-20 20:03                     ` Laszlo Ersek
     [not found]                   ` <8A1C7ED9-000A-4EBB-A196-10CE5B9B522F@citrix.com>
2019-03-21 17:41                     ` Laszlo Ersek
2019-03-18 18:17   ` Kinney, Michael D
2019-03-14 18:03 ` Jordan Justen
2019-03-18 18:25   ` Kinney, Michael D
2019-03-18 19:42     ` Jordan Justen
2019-03-19 17:58     ` Leif Lindholm
2019-03-19 19:09       ` Kinney, Michael D
2019-03-19 19:57         ` Jordan Justen
2019-03-19 20:06         ` Leif Lindholm

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-list 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=de78bacc-1b4c-c703-c5b0-6ddfd531c5aa@arm.com \
    --to=devel@edk2.groups.io \
    /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