From: "Fu, Siyuan" <siyuan.fu@intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Reminder for deleting 3 network drivers in MdeModulePkg
Date: Tue, 30 Oct 2018 08:11:52 +0000 [thread overview]
Message-ID: <B1FF2E9001CE9041BD10B825821D5BC58B678368@SHSMSX103.ccr.corp.intel.com> (raw)
Hi, All
This email is a reminder for the patch series "Delete TCP, PXE, iSCSI driver in MdeModulePkg" https://lists.01.org/pipermail/edk2-devel/2018-October/031605.html, which *intend to delete 3 network drivers from edk2 repository*. Please help to review this email and also the patch series to provide your feedback before this weekend.
Below is a driver list which we want to *delete* from edk2 master, because these drivers have not been actively maintained for a long time, and can't co-work with the dual-stack drivers in NetworkPkg.
MdeModulePkg/Universal/Network/Tcp4Dxe (will be deleted)
MdeModulePkg/Universal/Network/UefiPxeBcDxe (will be deleted)
MdeModulePkg/Universal/Network/IScsiDxe (will be deleted)
Below drivers in NetworkPkg contains all the functionalities compared with the MdeModulePkg version, with more bug fixes and more new feature added:
NetworkPkg/TcpDxe/TcpDxe.inf
NetworkPkg/UefiPxeBcDxe/UefiPxeBcDxe.inf
NetworkPkg/IScsiDxe/IScsiDxe.inf
People who want to continue use these deleted drivers could go to edk2/UDK2018 branch to get them, but it's *highly not recommended*.
*If you have any opposition on deleting these drivers, please let me know before this weekend, thanks.*
Bugzilla link for this issue:
https://bugzilla.tianocore.org/show_bug.cgi?id=1278
BestRegards
Fu Siyuan
next reply other threads:[~2018-10-30 8:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 8:11 Fu, Siyuan [this message]
2018-10-30 10:46 ` Reminder for deleting 3 network drivers in MdeModulePkg Leif Lindholm
2018-10-31 0:49 ` Fu, Siyuan
2018-10-31 2:58 ` Fu, Siyuan
2018-10-31 10:50 ` Leif Lindholm
2018-11-01 6:01 ` Gao, Liming
2018-11-01 9:01 ` Leif Lindholm
2018-11-02 14:21 ` Gao, Liming
2018-11-02 15:00 ` Andrew Fish
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=B1FF2E9001CE9041BD10B825821D5BC58B678368@SHSMSX103.ccr.corp.intel.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