From: Fu Siyuan <siyuan.fu@intel.com>
To: edk2-devel@lists.01.org
Subject: [Patch 0/5] Refine PXE driver code logic
Date: Tue, 2 Jan 2018 13:27:39 +0800 [thread overview]
Message-ID: <20180102052744.9928-1-siyuan.fu@intel.com> (raw)
See each patch file for details.
Fu Siyuan (5):
NetworkPkg: Abort the PXE process if DHCP has been started by other
instance.
NetworkPkg: Check allocated buffer pointer before use.
NetworkPkg: Fix memory leak problem in PXE driver.
NetworkPkg: Add assert for buffer pointer from DHCP driver.
NetworkPkg: Update PXE driver to check for NULL pointer before use it.
NetworkPkg/UefiPxeBcDxe/PxeBcDhcp4.c | 13 ++++++-------
NetworkPkg/UefiPxeBcDxe/PxeBcDhcp6.c | 32 +++++++++++++++++++++++++-------
NetworkPkg/UefiPxeBcDxe/PxeBcDriver.c | 5 ++++-
NetworkPkg/UefiPxeBcDxe/PxeBcImpl.c | 20 ++++++++------------
4 files changed, 43 insertions(+), 27 deletions(-)
--
2.13.0.windows.1
next reply other threads:[~2018-01-02 5:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 5:27 Fu Siyuan [this message]
2018-01-02 5:27 ` [Patch 1/5] NetworkPkg: Abort the PXE process if DHCP has been started by other instance Fu Siyuan
2018-01-02 5:27 ` [Patch 2/5] NetworkPkg: Check allocated buffer pointer before use Fu Siyuan
2018-01-02 6:26 ` Gary Lin
2018-01-02 5:27 ` [Patch 3/5] NetworkPkg: Fix memory leak problem in PXE driver Fu Siyuan
2018-01-02 5:27 ` [Patch 4/5] NetworkPkg: Add assert for buffer pointer from DHCP driver Fu Siyuan
2018-01-02 5:27 ` [Patch 5/5] NetworkPkg: Update PXE driver to check for NULL pointer before use it Fu Siyuan
2018-01-02 5:43 ` Subramanian, Sriram
2018-01-02 5:45 ` [Patch 0/5] Refine PXE driver code logic Subramanian, Sriram
2018-01-02 5:50 ` Subramanian, Sriram
2018-01-04 1:02 ` Fu, Siyuan
2018-01-02 6:59 ` Wu, Jiaxin
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=20180102052744.9928-1-siyuan.fu@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