From: Star Zeng <star.zeng@intel.com>
To: edk2-devel@lists.01.org
Cc: Star Zeng <star.zeng@intel.com>
Subject: [PATCH V3 0/3] Update comments and code for GetNextVariableName to follow UEFI 2.7
Date: Mon, 26 Jun 2017 17:20:50 +0800 [thread overview]
Message-ID: <1498468853-175036-1-git-send-email-star.zeng@intel.com> (raw)
V3: Remove the ((VariableName[MaxLen - 1] != 0) check and enhance the code comments
based on Ruiyu's feedback.
V2: Add changes for EmuVariable and FsVariable.
"The size must be large enough to fit input string supplied in
VariableName buffer" is added in the description for VariableNameSize.
And two cases of EFI_INVALID_PARAMETER are added.
1. The input values of VariableName and VendorGuid are not a name and
GUID of an existing variable.
2. Null-terminator is not found in the first VariableNameSize bytes of
the input VariableName buffer.
Star Zeng (3):
MdePkg: Update comments for GetNextVariableName to follow UEFI 2.7
MdeModulePkg Variable: Update GetNextVariableName to follow UEFI 2.7
DuetPkg FsVariable: Update GetNextVariableName to follow UEFI 2.7
DuetPkg/FSVariable/FSVariable.c | 31 ++++++++++++-
.../Universal/Variable/EmuRuntimeDxe/EmuVariable.c | 41 ++++++++++++++---
.../Variable/EmuRuntimeDxe/InitVariable.c | 24 ++++++----
.../Universal/Variable/EmuRuntimeDxe/Variable.h | 15 ++++---
.../Universal/Variable/RuntimeDxe/Variable.c | 51 +++++++++++++++++++---
.../Universal/Variable/RuntimeDxe/Variable.h | 25 ++++++++---
MdePkg/Include/Uefi/UefiSpec.h | 8 +++-
7 files changed, 160 insertions(+), 35 deletions(-)
--
2.7.0.windows.1
next reply other threads:[~2017-06-26 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 9:20 Star Zeng [this message]
2017-06-26 9:20 ` [PATCH V3 1/3] MdePkg: Update comments for GetNextVariableName to follow UEFI 2.7 Star Zeng
2017-06-26 9:20 ` [PATCH V3 2/3] MdeModulePkg Variable: Update " Star Zeng
2017-06-26 9:20 ` [PATCH V3 3/3] DuetPkg FsVariable: " Star Zeng
2017-06-27 3:22 ` Ni, Ruiyu
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=1498468853-175036-1-git-send-email-star.zeng@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