From: "Rebecca Cran" <rebecca@bsdio.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>,
Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: OvmfPkg: Adding support for bhyve as OvmfPkg/Bhyve
Date: Fri, 26 Jun 2020 09:38:09 -0600 [thread overview]
Message-ID: <92612908-44f4-30d4-ae3a-3ad595e2141f@bsdio.com> (raw)
I've finished the work to move BhyvePkg into OvmfPkg/Bhyve, and the
changes are available at
https://github.com/bcran/edk2/commit/09cfc08b50992ed3f76459611e8a928b74ed8c8a
.
Since it's such a large patch (over 400KB, but the vast majority of it
is existing changes from previously-reviewed patches), I'm posting a
link to the changes here in case there are any fundamental issues with
it before I post it for review.
I've run PatchCheck.py and the only issue it flagged is that the
'license' on VbeShim.h is wrong, and that's because the header is
non-standard:
//
// THIS FILE WAS GENERATED BY "VbeShim.sh". DO NOT EDIT.
//
--
Rebecca Cran
next reply other threads:[~2020-06-26 15:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 15:38 Rebecca Cran [this message]
2020-07-02 9:27 ` OvmfPkg: Adding support for bhyve as OvmfPkg/Bhyve Laszlo Ersek
2020-07-02 10:54 ` License Check - was " Leif Lindholm
2020-07-02 13:49 ` [edk2-devel] " Liming Gao
2020-07-02 14:13 ` Leif Lindholm
2020-07-02 14:31 ` Ard Biesheuvel
2020-07-03 1:40 ` Liming Gao
2020-07-03 10:37 ` Leif Lindholm
2020-07-03 15:07 ` Liming Gao
2020-07-03 15:49 ` Laszlo Ersek
2020-07-07 14:31 ` Liming Gao
2020-07-03 3:13 ` Rebecca Cran
2020-07-03 15:50 ` 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=92612908-44f4-30d4-ae3a-3ad595e2141f@bsdio.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