From: Hao Wu <hao.a.wu@intel.com>
To: edk2-devel@lists.01.org
Cc: Hao Wu <hao.a.wu@intel.com>, Ruiyu Ni <ruiyu.ni@intel.com>,
Yonghong Zhu <yonghong.zhu@intel.com>,
Liming Gao <liming.gao@intel.com>
Subject: [PATCH 0/5] BaseTools/Common & DevicePath: Code refinements
Date: Mon, 8 Jan 2018 13:30:39 +0800 [thread overview]
Message-ID: <20180108053044.11788-1-hao.a.wu@intel.com> (raw)
The series refines the C/C++ source codes within
BaseTools/C/Source/Common/ and BaseTools/Source/C/DevicePath/ for the
below catagories:
* Resolve possible resource/memory leaks
* Resolve possible NULL pointer dereferences
Cc: Ruiyu Ni <ruiyu.ni@intel.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Hao Wu (5):
BaseTools/C/Common: Fix code to be more readable
BaseTools/C/Common: Fix potential memory leak
BaseTools/DevicePath: Fix potential memory leak
BaseTools/C/Common: Fix potential null pointer dereference
BaseTools/DevicePath: Fix potential null pointer dereference
BaseTools/Source/C/Common/CommonLib.c | 2 +-
BaseTools/Source/C/Common/PcdValueCommon.c | 10 ++++++++++
BaseTools/Source/C/DevicePath/DevicePath.c | 6 ++++++
BaseTools/Source/C/DevicePath/DevicePathFromText.c | 11 +++++++++++
4 files changed, 28 insertions(+), 1 deletion(-)
--
2.12.0.windows.1
next reply other threads:[~2018-01-08 5:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 5:30 Hao Wu [this message]
2018-01-08 5:30 ` [PATCH 1/5] BaseTools/C/Common: Fix code to be more readable Hao Wu
2018-01-08 5:30 ` [PATCH 2/5] BaseTools/C/Common: Fix potential memory leak Hao Wu
2018-01-08 5:30 ` [PATCH 3/5] BaseTools/DevicePath: " Hao Wu
2018-01-08 5:30 ` [PATCH 4/5] BaseTools/C/Common: Fix potential null pointer dereference Hao Wu
2018-01-08 5:30 ` [PATCH 5/5] BaseTools/DevicePath: " Hao Wu
2018-01-11 3:09 ` [PATCH 0/5] BaseTools/Common & DevicePath: Code refinements Zhu, Yonghong
2018-01-12 1:00 ` Gao, Liming
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=20180108053044.11788-1-hao.a.wu@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