From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, hao.a.wu@intel.com
Cc: David Woodhouse <dwmw2@infradead.org>, Ray Ni <ray.ni@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [edk2-devel] [PATCH v2 00/10] Duplicate required CSM components for OVMF
Date: Tue, 28 May 2019 13:48:25 +0200 [thread overview]
Message-ID: <5bb0b7dc-a16e-3ff9-af6e-3c87c6e3744c@redhat.com> (raw)
In-Reply-To: <20190527030350.11996-1-hao.a.wu@intel.com>
On 05/27/19 05:03, Wu, Hao A wrote:
> '''
> Please note that this series will be hold until the edk2-stable201905 is
> created.
> '''
>
> The series is also available at:
> https://github.com/hwu25/edk2/tree/ovmf_csm_v2
>
> V2 changes:
>
> Discussion with David Woodhouse for him to take the reviewer role for the
> duplicated CSM components under OvmfPkg:
> https://edk2.groups.io/g/devel/topic/31682287#40996
>
> The (new) first patch will update the Maintainers.txt to reflect such
> role.
As noted earlier, I plan to review this series once David is happy with
it (in particular, with the first patch).
And, the following patch sets all depend on this one, directly or
indirectly:
[edk2-devel] [PATCH v1 0/6] Ovmf: Drop IntelFramework[Module]Pkg dependency
[edk2-devel] [RFC][PATCH v1 0/1] PcAtChipsetPkg: Remove framework modules
[edk2-devel] [RFC][PATCH v1 0/3] Remove IntelFramework[Module]Pkg
Of those, I plan to review at least the OvmfPkg one, once the
dependencies are all in place. Please ping me, should I forget.
(Yesterday I made an effort to set up the inter-BZ deps as well.)
Thanks,
Laszlo
next prev parent reply other threads:[~2019-05-28 11:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 3:03 [PATCH v2 00/10] Duplicate required CSM components for OVMF Wu, Hao A
2019-05-27 3:03 ` [PATCH v2 01/10] Maintainers.txt: Add maintainer for CSM components in OvmfPkg Wu, Hao A
2019-06-13 13:26 ` [edk2-devel] " Laszlo Ersek
2019-05-27 3:03 ` [PATCH v2 02/10] OvmfPkg: Copy the required CSM components from framework packages Wu, Hao A
2019-06-13 13:40 ` [edk2-devel] " Laszlo Ersek
2019-05-27 3:03 ` [PATCH v2 03/10] OvmfPkg/OvmfPkg.dec: Add definitions for CSM-related Guid & Protocol Wu, Hao A
2019-06-13 13:49 ` [edk2-devel] " Laszlo Ersek
2019-05-27 3:03 ` [PATCH v2 04/10] OvmfPkg/OvmfPkg.dec: Add the new include folder for CSM header files Wu, Hao A
2019-06-13 13:49 ` [edk2-devel] " Laszlo Ersek
2019-05-27 3:03 ` [PATCH v2 05/10] OvmfPkg/OvmfPkg.dec: Add PCD definitions used by copied CSM modules Wu, Hao A
2019-06-13 14:09 ` [edk2-devel] " Laszlo Ersek
2019-05-27 3:03 ` [PATCH v2 06/10] OvmfPkg/Csm/VideoDxe: Update to make it build for OVMF Wu, Hao A
2019-06-13 14:10 ` [edk2-devel] " Laszlo Ersek
2019-05-27 3:03 ` [PATCH v2 07/10] OvmfPkg/Csm/LegacyBiosDxe: " Wu, Hao A
2019-06-13 14:15 ` [edk2-devel] " Laszlo Ersek
2019-05-27 3:03 ` [PATCH v2 08/10] OvmfPkg/Csm/LegacyBootMaintUiLib: " Wu, Hao A
2019-06-13 14:16 ` [edk2-devel] " Laszlo Ersek
2019-05-27 3:03 ` [PATCH v2 09/10] OvmfPkg/Csm/LegacyBootManagerLib: " Wu, Hao A
2019-06-13 14:17 ` [edk2-devel] " Laszlo Ersek
2019-05-27 3:03 ` [PATCH v2 10/10] OvmfPkg: Update DSC/FDF files to consume CSM components in OvmfPkg Wu, Hao A
2019-06-13 14:22 ` [edk2-devel] " Laszlo Ersek
2019-05-28 11:48 ` Laszlo Ersek [this message]
2019-05-29 1:12 ` [edk2-devel] [PATCH v2 00/10] Duplicate required CSM components for OVMF Wu, Hao A
2019-06-03 9:29 ` Laszlo Ersek
2019-06-12 21:40 ` David Woodhouse
2019-06-14 5:08 ` [edk2-devel] " Wu, Hao A
2019-06-12 21:43 ` [PATCH 11/10] OvmfPkg/Csm/LegacyBiosDxe: Correct Legacy16GetTableAddress call for E820 data David Woodhouse
2019-06-13 6:28 ` [edk2-devel] " Wu, Hao A
2019-06-13 7:10 ` Ni, Ray
2019-06-13 7:40 ` Jordan Justen
2019-06-13 8:00 ` David Woodhouse
2019-06-13 8:34 ` David Woodhouse
2019-06-13 12:45 ` Laszlo Ersek
2019-06-13 8:40 ` [PATCH v2 11/10] OvmfPkg/Csm/LegacyBiosDxe: Fix " David Woodhouse
2019-06-13 14:23 ` [edk2-devel] " 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=5bb0b7dc-a16e-3ff9-af6e-3c87c6e3744c@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