From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124])
 by mx.groups.io with SMTP id smtpd.web10.48702.1606203182044214235
 for <devel@edk2.groups.io>;
 Mon, 23 Nov 2020 23:33:02 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Edil/N1a;
 spf=pass (domain: redhat.com, ip: 63.128.21.124, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1606203181;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=iLw2bQiRx+jD8v6KxrYHpeVNwBnSxY9poU/ZRbtcs+4=;
	b=Edil/N1aMRcpNqzBgau0HOY36wmDW1wupfHDaDwd6+n1MNP/qScRTLZ4u5n1xKD1x9bd4F
	bAlOEV8/AZLJLhpZJNKtMhG1Pj5vVjjUWAB3lJyo9iSOY7w88LbEd7HXBQnq2Gvuw6bHsB
	+8dj5BbsQ7W5n2Vq9z5C9dK0Hdx4TaU=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-460-hMc524VaOs2TXQ-10zJN6w-1; Tue, 24 Nov 2020 02:32:59 -0500
X-MC-Unique: hMc524VaOs2TXQ-10zJN6w-1
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 8A6E91005E5B;
	Tue, 24 Nov 2020 07:32:57 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-113-113.ams2.redhat.com [10.36.113.113])
	by smtp.corp.redhat.com (Postfix) with ESMTP id 238605C1A3;
	Tue, 24 Nov 2020 07:32:55 +0000 (UTC)
Subject: Re: [edk2-devel] [PATCH v2 0/3] various bhyve tweaks and updates
To: Rebecca Cran <rebecca@bsdio.com>, devel@edk2.groups.io
Cc: Jordan Justen <jordan.l.justen@intel.com>,
 Ard Biesheuvel <ard.biesheuvel@arm.com>, Peter Grehan <grehan@freebsd.org>
References: <20201124005733.18107-1-rebecca@bsdio.com>
 <3496af87-f723-6cf9-c0dd-916c711e5a84@redhat.com>
 <d1ddd96e-a2f5-8299-d1ad-9169a8295a01@bsdio.com>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <1ae00ed4-7761-5940-1fb2-ed82e3c02a1b@redhat.com>
Date: Tue, 24 Nov 2020 08:32:55 +0100
MIME-Version: 1.0
In-Reply-To: <d1ddd96e-a2f5-8299-d1ad-9169a8295a01@bsdio.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16
Authentication-Results: relay.mimecast.com;
	auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit

On 11/24/20 02:19, Rebecca Cran wrote:
> 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 :)
> 
> 

OK, thanks!
Laszlo