From: Laszlo Ersek <lersek@redhat.com>
To: Fu Siyuan <siyuan.fu@intel.com>
Cc: edk2-devel@lists.01.org, Ting Ye <ting.ye@intel.com>,
Jiaxin Wu <jiaxin.wu@intel.com>
Subject: Re: [PATCH 1/6] NetworkPkg: Add DSC/FDF include segment files to NetworkPkg.
Date: Wed, 21 Nov 2018 11:56:04 +0100 [thread overview]
Message-ID: <f659c43b-bcd4-acbb-9fcc-06c488066d32@redhat.com> (raw)
In-Reply-To: <1f37c165-aa7e-03d2-218d-b0c394c1e2fe@redhat.com>
On 11/21/18 11:46, Laszlo Ersek wrote:
> On 11/21/18 06:28, Fu Siyuan wrote:
>> The "Network.dsc.inc" and "Network.fdf.inc" are added for platform owner to
>> easily enable/disable network stack support on their platform, by adding
>> !include NetworkPkg/Network.dsc.inc
>> and
>> !include NetworkPkg/Network.fdf.inc
>> to their platform DSC/FDF files.
>>
>> A set of flags can be changed before the include line or in build command
>> line ("-D FLAG=VALUE") to enable or disable related feature set.
>>
>> The default value of these flags are:
>> DEFINE NETWORK_ENABLE = TRUE
>> DEFINE NETWORK_SNP_ENABLE = TRUE
>> DEFINE NETWORK_IP4_ENABLE = TRUE
>> DEFINE NETWORK_IP6_ENABLE = TRUE
>> DEFINE NETWORK_TLS_ENABLE = TRUE
>> DEFINE NETWORK_HTTP_BOOT_ENABLE = TRUE
>> DEFINE NETWORK_ALLOW_HTTP_CONNECTIONS = FALSE
>> DEFINE NETWORK_IPSEC_ENABLE = TRUE
>> DEFINE NETWORK_ISCSI_ENABLE = TRUE
>> DEFINE NETWORK_VLAN_ENABLE = TRUE
>
> [...]
I'd like to review the ArmVirtPkg and OvmfPkg patches in detail once the
NetworkPkg patch stabilizes.
In addition, I have some higher-level comments. This patch series
effectively renames a few preexistent build flags, such as
"HTTP_BOOT_ENABLE" to "NETWORK_HTTP_BOOT_ENABLE", "TLS_ENABLE" to
"NETWORK_TLS_ENABLE", and so on.
- Please grep the edk2 source tree for the original (disappearing)
flags, and update them as necessary, not just in DSC/FDF files, but also
in documentation. For example, "HTTP_BOOT_ENABLE" and "TLS_ENABLE" are
mentioned in "OvmfPkg/README".
- Please also grep the edk2 Wiki for the same (clone it locally and then
run "git grep"). For example, the
"Testing-SMM-with-QEMU,-KVM-and-libvirt.md" article also refers to
HTTP_BOOT_ENABLE and TLS_ENABLE.
- It is likely a good idea to list this change (that is,
<https://bugzilla.tianocore.org/show_bug.cgi?id=1293>), under
<https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning#proposed-features-1>.
I see that #1278 is listed already, but the build flag renaming is an
incompatible change, and it deserves a mention.
Thanks!
Laszlo
next prev parent reply other threads:[~2018-11-21 10:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 5:28 [PATCH 0/6] Add DSC/FDF include segment files for network stack Fu Siyuan
2018-11-21 5:28 ` [PATCH 1/6] NetworkPkg: Add DSC/FDF include segment files to NetworkPkg Fu Siyuan
2018-11-21 10:46 ` Laszlo Ersek
2018-11-21 10:56 ` Laszlo Ersek [this message]
2018-11-21 11:53 ` Fu, Siyuan
2018-11-21 15:32 ` Laszlo Ersek
2018-11-21 5:28 ` [PATCH 2/6] Nt32Pkg: Update DSC/FDF to use NetworkPkg's include fragment file Fu Siyuan
2018-11-21 5:28 ` [PATCH 3/6] ArmVirtPkg: " Fu Siyuan
2018-11-21 11:26 ` Laszlo Ersek
2018-11-21 5:28 ` [PATCH 4/6] EmulatorPkg: " Fu Siyuan
2018-11-21 5:28 ` [PATCH 5/6] OvmfPkg: " Fu Siyuan
2018-11-21 11:07 ` Laszlo Ersek
2018-11-21 5:28 ` [PATCH 6/6] Vlv2TbltDevicePkg: " Fu Siyuan
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=f659c43b-bcd4-acbb-9fcc-06c488066d32@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