From: Star Zeng <star.zeng@intel.com>
To: edk2-devel@lists.01.org
Cc: Star Zeng <star.zeng@intel.com>
Subject: [PATCH 0/2] Update comments and code for GetNextVariableName to follow UEFI 2.7
Date: Thu, 22 Jun 2017 21:35:16 +0800 [thread overview]
Message-ID: <1498138518-151584-1-git-send-email-star.zeng@intel.com> (raw)
"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 (2):
MdePkg: Update comments for GetNextVariableName to follow UEFI 2.7
MdeModulePkg Variable: Update GetNextVariableName to follow UEFI 2.7
MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c | 19 +++++++++++++++++++
MdePkg/Include/Uefi/UefiSpec.h | 7 ++++++-
2 files changed, 25 insertions(+), 1 deletion(-)
--
2.7.0.windows.1
next reply other threads:[~2017-06-22 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 13:35 Star Zeng [this message]
2017-06-22 13:35 ` [PATCH 1/2] MdePkg: Update comments for GetNextVariableName to follow UEFI 2.7 Star Zeng
2017-06-22 13:35 ` [PATCH 2/2] MdeModulePkg Variable: Update " Star Zeng
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=1498138518-151584-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