From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, shenglei.zhang@intel.com
Subject: Re: [edk2-devel] [PATCH 0/4] Add DSC/FDF include segment files for network stack
Date: Tue, 14 May 2019 14:43:20 +0200 [thread overview]
Message-ID: <a1a65454-0e8e-cb50-ed41-a8ce8e40a47d@redhat.com> (raw)
In-Reply-To: <20190514073938.21528-1-shenglei.zhang@intel.com>
On 05/14/19 09:39, Zhang, Shenglei wrote:
> There is a patch to remove the redudant IP4 only iSCSI/PXE/TCP drivers
> from MdeModulePkg, which has been reviewed before edk2-stable201811 tag.
> And we also have plan to move all network related libraries/modules to
> NetworkPkg. In order to make these change more smoothly, 2 configuration
> fragment files are provided for platform to enable the network stack
> support, without directly reference the INF module path.
> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=1293
>
> Fu Siyuan (4):
> OvmfPkg: Update DSC/FDF to use NetworkPkg's include fragment file.
> Nt32Pkg: Update DSC/FDF to use NetworkPkg's include fragment file.
> ArmVirtPkg: Update DSC/FDF to use NetworkPkg's include fragment file.
> EmulatorPkg: Update DSC/FDF to use NetworkPkg's include fragment file.
>
> ArmVirtPkg/ArmVirt.dsc.inc | 10 +---
> ArmVirtPkg/ArmVirtQemu.dsc | 43 +++++-----------
> ArmVirtPkg/ArmVirtQemuFvMain.fdf.inc | 25 +---------
> ArmVirtPkg/ArmVirtQemuKernel.dsc | 43 +++++-----------
> EmulatorPkg/EmulatorPkg.dsc | 32 ++++++------
> EmulatorPkg/EmulatorPkg.fdf | 10 +---
> Nt32Pkg/Nt32Pkg.dsc | 75 +++-------------------------
> Nt32Pkg/Nt32Pkg.fdf | 27 +---------
> OvmfPkg/OvmfPkgIa32.dsc | 70 ++++++++------------------
> OvmfPkg/OvmfPkgIa32.fdf | 29 +----------
> OvmfPkg/OvmfPkgIa32X64.dsc | 71 ++++++++------------------
> OvmfPkg/OvmfPkgIa32X64.fdf | 29 +----------
> OvmfPkg/OvmfPkgX64.dsc | 69 ++++++++-----------------
> OvmfPkg/OvmfPkgX64.fdf | 29 +----------
> 14 files changed, 121 insertions(+), 441 deletions(-)
>
Two general comments:
(1) We have 4 (not 2) include fragments for the DSC (Defines, Libs,
Pcds, Components).
This is not really relevant for any of the patches, but it could help
with clarifying the blurb, if a v2 is needed.
(2) The blurb states that the patches were originally authored by Fu
Siyuan. However, the patches themselves don't start with "From: Fu
Siyuan ...".
This makes me think that the blurb is out of sync with the patches
themselves, to some extent.
Thanks
Laszlo
next prev parent reply other threads:[~2019-05-14 12:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 7:39 [PATCH 0/4] Add DSC/FDF include segment files for network stack Zhang, Shenglei
2019-05-14 7:39 ` [PATCH 1/4] OvmfPkg: Update DSC/FDF to use NetworkPkg's include fragment file Zhang, Shenglei
2019-05-14 12:55 ` [edk2-devel] " Liming Gao
2019-05-14 13:48 ` Laszlo Ersek
2019-05-15 7:02 ` Zhang, Shenglei
2019-05-15 8:10 ` Laszlo Ersek
2019-05-14 7:39 ` [PATCH 2/4] Nt32Pkg: " Zhang, Shenglei
2019-05-14 12:44 ` Ni, Ray
2019-05-14 7:39 ` [PATCH 3/4] ArmVirtPkg: " Zhang, Shenglei
2019-05-14 14:22 ` [edk2-devel] " Laszlo Ersek
2019-05-14 7:39 ` [PATCH 4/4] EmulatorPkg: " Zhang, Shenglei
2019-05-14 12:44 ` [edk2-devel] " Ni, Ray
2019-05-14 12:43 ` Laszlo Ersek [this message]
2019-05-14 12:59 ` [edk2-devel] [PATCH 0/4] Add DSC/FDF include segment files for network stack Liming Gao
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=a1a65454-0e8e-cb50-ed41-a8ce8e40a47d@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