From: "Rebecca Cran" <rebecca@bsdio.com>
To: Laszlo Ersek <lersek@redhat.com>, devel@edk2.groups.io
Cc: 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: [PATCH v3 0/6] Add BhyvePkg, to support the bhyve hypervisor
Date: Tue, 21 Apr 2020 09:38:34 -0600 [thread overview]
Message-ID: <de5d6752-13ea-bef7-ed09-383cb5ff22de@bsdio.com> (raw)
In-Reply-To: <fd27f965-f730-749e-a156-b67e6b4e676b@redhat.com>
On 4/21/20 9:27 AM, Laszlo Ersek wrote:
>
> (1) For example, I can't find the patch that adds
> "BhyvePkg/BhyvePkgX64.dsc", in spite of the file being listed in the
> cumulative diffstat below.
That's in the "Add BhyvePkg" patch.
> (2) I also don't really understand why v2 / v3 have been posted, given
> that the bhyve-specific ResetSystemLib instance that I suggested under
> v1, based on your proposed code, still depends on the ResetSystemLib
> cleanup series that I posted. The idea is that you would base the new
> bhyve ResetSystemLib instance on my ResetSystemLib refactoring.
Since the changes to ResetSystemLib aren't required for this series and
will require rework, I removed them.
> Because my series has not been merged yet, for such a bhyve rebase you'd
> have to pick up my patches from the list temporarily. That's a 100%
> usable approach, but then, this v3 series of yours does not seem to
> introduce *any* ResetSystemLib instance. Have you decided to postpone
> that work for later?
Sorry, yes I have decided to postpone those changes since as you say I'd
need to pick up your patches from the list.
> In the end, please wait until I get around merging the ResetSystemLib
> refactoring <https://bugzilla.tianocore.org/show_bug.cgi?id=2675>.
I'd prefer not to, since introducing BhyvePkg doesn't depend on the
ResetSystemLib changes. Could this series not be committed, then a
subsequent commit be made to use the ResetSystemLib changes?
> Then,
> please post a new, comprehensive bhyve set. Patch sets pending review on
> a mailing list are not incremental; new versions entirely supersede
> earlier versions. Patches are considered incremental only when (a)
> earlier patches have been merged, or (b) there's an agreement that in
> the particular situation a new patch (or a few patches) can be appended
> to a pending series.
I totally understand that. Both the v2 and v3 patch series are
independent and comprehensive (except for the removal of the
ResetSystemLib changes, and combining a couple of changes together that
didn't need to be separate).
--
Rebecca Cran
next prev parent reply other threads:[~2020-04-21 15:38 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
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 [this message]
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=de5d6752-13ea-bef7-ed09-383cb5ff22de@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