public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, lersek@redhat.com
Cc: Jordan Justen <jordan.l.justen@intel.com>,
	Ard Biesheuvel <ard.biesheuvel@arm.com>,
	Peter Grehan <grehan@freebsd.org>
Subject: Re: [edk2-devel] [PATCH v2 0/3] various bhyve tweaks and updates
Date: Mon, 23 Nov 2020 18:19:30 -0700	[thread overview]
Message-ID: <d1ddd96e-a2f5-8299-d1ad-9169a8295a01@bsdio.com> (raw)
In-Reply-To: <3496af87-f723-6cf9-c0dd-916c711e5a84@redhat.com>

On 11/23/20 6:04 PM, Laszlo Ersek wrote:
>
> Can this whole set wait until after edk2-stable202011, or would you like
> me to merge patch#1 ("OvmfPkg/Bhyve: Add VariablePolicy engine to
> Bhyve") in isolation, during the Hard Feature Freeze? (It definitely
> qualifies, because it fixes a build regression caused by the patches for
> TianoCore#2522.)
>
> I don't think we should merge patches #2 and #3 during the HFF.

I'm not sure it makes sense to have patch #1 without #3 to make it 
usable on AMD, so let's leave the whole set until after the stable tag. 
We can leave bhyve users on 2014.SP1 firmware a few days longer :)


-- 
Rebecca Cran



  reply	other threads:[~2020-11-24  1:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24  0:57 [PATCH v2 0/3] various bhyve tweaks and updates Rebecca Cran
2020-11-24  0:57 ` [PATCH v2 1/3] OvmfPkg/Bhyve: Add VariablePolicy engine to Bhyve Rebecca Cran
2020-11-24  0:57 ` [PATCH v2 2/3] OvmfPkg/Bhyve: Add support for the AMD host bridge Rebecca Cran
2020-11-24  0:57 ` [PATCH v2 3/3] OvmfPkg/Bhyve: Copy Real16ToFlat32.asm and enable cache in CR0 Rebecca Cran
2020-11-24  1:04 ` [PATCH v2 0/3] various bhyve tweaks and updates Laszlo Ersek
2020-11-24  1:19   ` Rebecca Cran [this message]
2020-11-24  7:32     ` [edk2-devel] " Laszlo Ersek
2020-11-27 16:57     ` 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=d1ddd96e-a2f5-8299-d1ad-9169a8295a01@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