public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: "Zeng, Star" <star.zeng@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Zeng, Star" <star.zeng@intel.com>
Subject: Re: [PATCH V2 0/3] Update comments and code for GetNextVariableName to follow UEFI 2.7
Date: Fri, 23 Jun 2017 08:10:47 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D74DF3D@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1498205290-157888-1-git-send-email-star.zeng@intel.com>

Reviewed-by: Liming Gao <liming.gao@intel.com>

>-----Original Message-----
>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Star
>Zeng
>Sent: Friday, June 23, 2017 4:08 PM
>To: edk2-devel@lists.01.org
>Cc: Zeng, Star <star.zeng@intel.com>
>Subject: [edk2] [PATCH V2 0/3] Update comments and code for
>GetNextVariableName to follow UEFI 2.7
>
>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                    | 21 +++++++++++++++++-
> .../Universal/Variable/EmuRuntimeDxe/EmuVariable.c | 25
>+++++++++++++++++++++-
> .../Universal/Variable/RuntimeDxe/Variable.c       | 19 ++++++++++++++++
> MdePkg/Include/Uefi/UefiSpec.h                     |  7 +++++-
> 4 files changed, 69 insertions(+), 3 deletions(-)
>
>--
>2.7.0.windows.1
>
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org
>https://lists.01.org/mailman/listinfo/edk2-devel


      parent reply	other threads:[~2017-06-23  8:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23  8:08 [PATCH V2 0/3] Update comments and code for GetNextVariableName to follow UEFI 2.7 Star Zeng
2017-06-23  8:08 ` [PATCH V2 1/3] MdePkg: Update comments " Star Zeng
2017-06-23  8:08 ` [PATCH V2 2/3] MdeModulePkg Variable: Update " Star Zeng
2017-06-23  8:08 ` [PATCH V2 3/3] DuetPkg FsVariable: " Star Zeng
2017-06-23  8:20   ` Ni, Ruiyu
2017-06-23  9:33     ` Zeng, Star
2017-06-24  2:07       ` Ni, Ruiyu
2017-06-26  3:04         ` Zeng, Star
2017-06-26  5:36           ` Ni, Ruiyu
2017-06-26  5:41             ` Zeng, Star
2017-06-26  5:46               ` Ni, Ruiyu
2017-06-26  5:52                 ` Zeng, Star
2017-06-26  6:18                   ` Ni, Ruiyu
2017-06-26  6:31                     ` Zeng, Star
2017-06-23  8:10 ` Gao, Liming [this message]

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=4A89E2EF3DFEDB4C8BFDE51014F606A14D74DF3D@shsmsx102.ccr.corp.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