public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Lars Kurth <lars.kurth@citrix.com>,
	Laszlo Ersek <lersek@redhat.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>
Subject: Re: PATCH] Change EDK II to BSD+Patent License
Date: Fri, 15 Mar 2019 09:35:25 +0000	[thread overview]
Message-ID: <b897ca36-ebde-094c-ba18-6b1d2773d210@arm.com> (raw)
In-Reply-To: <8F40F2BF-B40F-4338-A832-70AE84B26408@citrix.com>

Hi Lars,

On 14/03/2019 20:04, Lars Kurth wrote:
> 
> 
> On 14/03/2019, 12:07, "Julien Grall" <julien.grall@arm.com> wrote:
> 
>      (+ Lars)
>      
>      On 3/14/19 10:55 AM, Laszlo Ersek wrote:
>      > On 03/13/19 18:54, Kinney, Michael D wrote:
>      > (2.2.2) Files that seem to be covered by the MIT license.
>      >
>      >            OvmfPkg/Include/IndustryStandard/Xen/arch-arm/xen.h
> ...
>      >            OvmfPkg/XenBusDxe/XenStore.h
>      >
>      >          It's OK to leave these untouched, for now. Later, we should
>      >          probably replace their license blocks with
>      >          "SPDX-License-Identifier: MIT" (as appropriate). It might make
>      >          sense to file a TianoCore BZ about them immediately, with a
>      >          BZ-dependency on BZ#1373.
>      
>      I have added Lars Kurth to confirm the license.
> 
> Can you give me some context? It's not clear to me what you expect me to do.

EDK2 is converting the full copyright in each file to SDPX identifier. While the 
copyright looks like an MIT license, it has never been confirmed. Andrew Cooper 
suggested you might be able to confirm.

Cheers,

-- 
Julien Grall


  parent reply	other threads:[~2019-03-15  9:35 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 [this message]
     [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
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=b897ca36-ebde-094c-ba18-6b1d2773d210@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