From: "Laszlo Ersek" <lersek@redhat.com>
To: Rebecca Cran <rebecca@bsdio.com>
Cc: devel@edk2.groups.io, Jordan Justen <jordan.l.justen@intel.com>,
Ard Biesheuvel <ard.biesheuvel@arm.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
Michael Kinney <michael.d.kinney@intel.com>,
Andrew Fish <afish@apple.com>, Peter Grehan <grehan@freebsd.org>
Subject: Re: [edk2-devel] [PATCH v3 4/6] Add BhyvePkg, to support the bhyve hypervisor
Date: Fri, 24 Apr 2020 14:22:35 +0200 [thread overview]
Message-ID: <143ef5ab-49a8-713c-62c1-02ebd6e3a4fd@redhat.com> (raw)
In-Reply-To: <02A78AC1-573F-4C7A-8466-5EA8885A3195@bsdio.com>
On 04/24/20 07:54, Rebecca Cran wrote:
>
>> On Apr 23, 2020, at 3:42 AM, Laszlo Ersek <lersek@redhat.com> wrote:
>>
>> BUt, I *think* the language seen in "OvmfPkg/License.txt" should
>> accommodate that too. It goes:
>>
>> Some files are subject to the following license, the [...] license.
>> Those files are located in:
>> - [directory]
>> - [directory]
>>
>> It says "some files", and where they are. It doesn't seem to imply that
>> *all* files under those directories are covered by the non-default license.
>>
>> So please just list all those module directories in this (non-default)
>> part of "BhyvePkg/License.txt" that have *at least one* file covered by
>> "BSD-2-Clause".
>
>
> Would it also be ok to use the following language?
>
> Some files are subject to the following license, the BSD-2-Clause license.
> Those files are located in:
>
> AcpiPlatformDxe/Bhyve.c
> PlatformPei/MemDetect.c
> PlatformPei/Platform.c
probably "located *at*" (not "in"), if we are listing the files
themselves. And yes, this is entirely OK, as long as you can collect
those files individually!
> I think I’ve fixed the rest of the changes you’ve requested. I’m ready to send the v4 series once I get clarification about whether I should add my own copyright line to files I’ve copied from OvmfPkg and made no changes to, or only deletions or other very minor changes.
I've attempted to answer that under your other email.
Thanks!
Laszlo
next prev parent reply other threads:[~2020-04-24 12:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 3:09 [PATCH v3 0/6] Add BhyvePkg, to support the bhyve hypervisor Rebecca Cran
2020-04-21 3:09 ` [PATCH v3 1/6] OvmfPkg: Add bhyve support into AcpiTimerLib Rebecca Cran
2020-04-23 7:56 ` [edk2-devel] " Laszlo Ersek
2020-04-21 3:09 ` [PATCH v3 2/6] OvmfPkg: Add QemuFwCfgLibNull Rebecca Cran
2020-04-23 8:21 ` [edk2-devel] " Laszlo Ersek
2020-04-21 3:09 ` [PATCH v3 3/6] OvmfPkg: Add VBE2 mode info structure to LegacyVgaBios.h Rebecca Cran
2020-04-23 8:05 ` [edk2-devel] " Laszlo Ersek
2020-04-21 3:09 ` [PATCH v3 4/6] Add BhyvePkg, to support the bhyve hypervisor Rebecca Cran
2020-04-23 9:19 ` [edk2-devel] " Laszlo Ersek
2020-04-23 9:42 ` Laszlo Ersek
2020-04-24 5:54 ` Rebecca Cran
2020-04-24 12:22 ` Laszlo Ersek [this message]
2020-04-23 20:08 ` Rebecca Cran
2020-04-24 10:11 ` Laszlo Ersek
2020-04-24 16:00 ` Rebecca Cran
2020-04-21 3:09 ` [PATCH v3 5/6] BhyvePkg: Add PlatformPei Rebecca Cran
2020-04-23 9:24 ` [edk2-devel] " Laszlo Ersek
2020-04-21 3:09 ` [PATCH v3 6/6] BhyvePkg: Add AcpiPlatformDxe Rebecca Cran
2020-04-23 9:44 ` [edk2-devel] " Laszlo Ersek
2020-04-21 15:27 ` [PATCH v3 0/6] Add BhyvePkg, to support the bhyve hypervisor Laszlo Ersek
2020-04-21 15:38 ` Rebecca Cran
2020-04-22 15:21 ` Laszlo Ersek
2020-04-22 16:48 ` Rebecca Cran
2020-04-24 10:11 ` Laszlo Ersek
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=143ef5ab-49a8-713c-62c1-02ebd6e3a4fd@redhat.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