public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wu, Hao A" <hao.a.wu@intel.com>
To: "Dong, Eric" <eric.dong@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch 0/2] Fix 2 regression caused by enabling pyrite 2.0 feature changes.
Date: Mon, 14 May 2018 08:25:25 +0000	[thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A0931D9B1D9@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20180514073601.9700-1-eric.dong@intel.com>

Reviewed-by: Hao Wu <hao.a.wu@intel.com>

Best Regards,
Hao Wu


> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Eric
> Dong
> Sent: Monday, May 14, 2018 3:36 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [Patch 0/2] Fix 2 regression caused by enabling pyrite 2.0
> feature changes.
> 
> Fix GCC build failure and PSID revert no hint message issues caused
> by enabling pyrite 2.0 feature.
> 
> Eric Dong (2):
>   SecurityPkg/TcgStorageOpalLib: Fix GCC build failure.
>   SecurityPkg/OpalPassword: Fix PSID revert no hint message.
> 
>  .../Library/TcgStorageOpalLib/TcgStorageOpalCore.c |  4 ---
>  .../TcgStorageOpalLib/TcgStorageOpalLibInternal.h  |  1 -
>  SecurityPkg/Tcg/Opal/OpalPassword/OpalDriver.c     | 29 +++++++++++++++---
> ----
>  3 files changed, 20 insertions(+), 14 deletions(-)
> 
> --
> 2.15.0.windows.1
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      parent reply	other threads:[~2018-05-14  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14  7:35 [Patch 0/2] Fix 2 regression caused by enabling pyrite 2.0 feature changes Eric Dong
2018-05-14  7:36 ` [Patch 1/2] SecurityPkg/TcgStorageOpalLib: Fix GCC build failure Eric Dong
2018-05-14  7:36 ` [Patch 2/2] SecurityPkg/OpalPassword: Fix PSID revert no hint message Eric Dong
2018-05-14  8:25 ` Wu, Hao A [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=B80AF82E9BFB8E4FBD8C89DA810C6A0931D9B1D9@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