From: "wenyi,xie" <xiewenyi2@huawei.com>
To: <devel@edk2.groups.io>, <jian.j.wang@intel.com>,
<hao.a.wu@intel.com>, <dandan.bi@intel.com>,
<eric.dong@intel.com>
Cc: <songdongkuang@huawei.com>, <xiewenyi2@huawei.com>
Subject: [PATCH EDK2 v1 0/1] MdeModulePkg/FileExplorerLib: remove redundant null pointer check
Date: Wed, 25 Nov 2020 09:52:50 +0800 [thread overview]
Message-ID: <1606269171-21979-1-git-send-email-xiewenyi2@huawei.com> (raw)
Main Changes :
Since Info is a pointer of struct EFI_FILE_SYSTEM_VOLUME_LABEL,
and this struct has only one member VolumeLabel which is char
array. So Info and Info->VolumeLabel are point to the same
address, and if Info != NULL, Info->VolumeLabel == NULL is
always false, it's no necessary to do null pointer check again.
Wenyi Xie (1):
MdeModulePkg/FileExplorerLib: remove redundant null pointer check
MdeModulePkg/Library/FileExplorerLib/FileExplorer.c | 10 +++-------
1 file changed, 3 insertions(+), 7 deletions(-)
--
2.20.1.windows.1
next reply other threads:[~2020-11-25 1:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 1:52 wenyi,xie [this message]
2020-11-25 1:52 ` [PATCH EDK2 v1 1/1] MdeModulePkg/FileExplorerLib: remove redundant null pointer check wenyi,xie
2020-11-25 3:26 ` 回复: [edk2-devel] " gaoliming
2020-11-25 15:01 ` Laszlo Ersek
2020-11-26 1:33 ` wenyi,xie
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=1606269171-21979-1-git-send-email-xiewenyi2@huawei.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