public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: "Wu, Hao A" <hao.a.wu@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH 0/2] MdePkg/Include: Reflect latest spec revision
Date: Thu, 14 Dec 2017 05:59:22 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E19215E@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20171214005936.2020-1-hao.a.wu@intel.com>

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

> -----Original Message-----
> From: Wu, Hao A
> Sent: Thursday, December 14, 2017 9:00 AM
> To: edk2-devel@lists.01.org
> Cc: Wu, Hao A <hao.a.wu@intel.com>; Gao, Liming <liming.gao@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>
> Subject: [PATCH 0/2] MdePkg/Include: Reflect latest spec revision
> 
> The series updates the header files within:
>   MdePkg/Include/Pi/
>   MdePkg/Include/Uefi/
> 
> to reflect the latest revision of the PI & UEFI spec respectively.
> 
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> 
> Hao Wu (2):
>   MdePkg/UefiSpec.h: Update the UEFI version to reflect new revision
>   MdePkg/Include/Pi: Modify specification number encoding
> 
>  MdePkg/Include/Pi/PiDxeCis.h   | 6 +++---
>  MdePkg/Include/Pi/PiPeiCis.h   | 4 ++--
>  MdePkg/Include/Uefi/UefiSpec.h | 7 ++++---
>  3 files changed, 9 insertions(+), 8 deletions(-)
> 
> --
> 2.12.0.windows.1



      parent reply	other threads:[~2017-12-14  5:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  0:59 [PATCH 0/2] MdePkg/Include: Reflect latest spec revision Hao Wu
2017-12-14  0:59 ` [PATCH 1/2] MdePkg/UefiSpec.h: Update the UEFI version to reflect new revision Hao Wu
2017-12-14  0:59 ` [PATCH 2/2] MdePkg/Include/Pi: Modify specification number encoding Hao Wu
2017-12-14  5:59 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14E19215E@SHSMSX104.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