From: Laszlo Ersek <lersek@redhat.com>
To: Fu Siyuan <siyuan.fu@intel.com>
Cc: edk2-devel@lists.01.org, Ruiyu Ni <ruiyu.ni@intel.com>,
Ting Ye <ting.ye@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Hao Wu <hao.a.wu@intel.com>, Jiaxin Wu <jiaxin.wu@intel.com>,
Anthony Perard <anthony.perard@citrix.com>,
David Wei <david.wei@intel.com>
Subject: Re: [PATCH v2 0/6] Add DSC/FDF include segment files for network stack
Date: Thu, 22 Nov 2018 17:12:10 +0100 [thread overview]
Message-ID: <e6377d60-ed2f-c276-9dd1-f4e6e8b0dde3@redhat.com> (raw)
In-Reply-To: <20181122052153.89464-1-siyuan.fu@intel.com>
On 11/22/18 06:21, Fu Siyuan 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, a set of fragment
> files (2 for DSC and 1 for FDF) are provided for platform to enable the
> network stack support, without directly reference the INF module path.
>
> Patch 1/6 adds centralized dsc/fdf include files to NetworkPkg, with
> a set of flags for feature set enable/disable.
> Patch 2~6 updates edk2 platform dsc/fdf files to use the new include
> files, instead of reference the module INF.
>
> v2:
> 1. Split the "Network.dsc.inc" in to 4 files for different sections in DSC
> file. This could provide more flexibility to platform owner to use the
> include files.
> 2. Clarify the OpenSSL dependency of TLS, iSCSI and IPsec enable flag.
> 3. Use "!error" statement for incorrect flag value check.
> 4. Update platform DSC/FDF to use the new include files.
> 5. Other decoration work according to Laszlo's comments.
Thanks for v2! I'll need a bit more time for reviewing it. Also it seems
we'll have to come to an agreement with Liming and Ray first. So let's
continue those sub-threads on the design ideas before I start my full v2
review round.
Thanks for your patience,
Laszlo
prev parent reply other threads:[~2018-11-22 16:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 5:21 [PATCH v2 0/6] Add DSC/FDF include segment files for network stack Fu Siyuan
2018-11-22 5:21 ` [PATCH v2 1/6] NetworkPkg: Add DSC/FDF include segment files to NetworkPkg Fu Siyuan
2018-11-22 9:56 ` Ni, Ruiyu
2018-11-22 10:52 ` Fu, Siyuan
2018-11-23 10:56 ` Laszlo Ersek
2018-12-10 8:36 ` Ard Biesheuvel
2018-12-10 14:40 ` Laszlo Ersek
2018-12-10 16:39 ` Ard Biesheuvel
2018-11-22 5:21 ` [PATCH v2 2/6] Nt32Pkg: Update DSC/FDF to use NetworkPkg's include fragment file Fu Siyuan
2018-11-22 5:21 ` [PATCH v2 3/6] ArmVirtPkg: " Fu Siyuan
2018-11-23 12:29 ` Laszlo Ersek
2018-11-23 12:30 ` Laszlo Ersek
2018-11-23 16:50 ` Laszlo Ersek
2018-11-22 5:21 ` [PATCH v2 4/6] EmulatorPkg: " Fu Siyuan
2018-11-22 5:21 ` [PATCH v2 5/6] OvmfPkg: " Fu Siyuan
2018-11-23 12:00 ` Laszlo Ersek
2018-11-23 12:10 ` Laszlo Ersek
2018-11-23 12:19 ` Laszlo Ersek
2018-11-22 5:21 ` [PATCH v2 6/6] Vlv2TbltDevicePkg: " Fu Siyuan
2018-11-22 6:14 ` [PATCH v2 0/6] Add DSC/FDF include segment files for network stack Gao, Liming
2018-11-22 15:48 ` Laszlo Ersek
2018-11-23 16:02 ` Gao, Liming
2018-11-23 18:35 ` Laszlo Ersek
2018-11-26 3:31 ` Gao, Liming
2018-11-26 11:34 ` Laszlo Ersek
2018-11-22 16:12 ` Laszlo Ersek [this message]
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=e6377d60-ed2f-c276-9dd1-f4e6e8b0dde3@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