public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: edk2-devel-01 <edk2-devel@lists.01.org>
Cc: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
	"Chao Zhang" <chao.b.zhang@intel.com>,
	"Jiewen Yao" <jiewen.yao@intel.com>,
	"Jordan Justen" <jordan.l.justen@intel.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [PATCH 0/2] OvmfPkg, SecurityPkg: small followup patches after the TPM2 addition to OVMF
Date: Fri,  9 Mar 2018 21:05:23 +0100	[thread overview]
Message-ID: <20180309200525.27376-1-lersek@redhat.com> (raw)

Repo:   https://github.com/lersek/edk2.git
Branch: ovmf_tcg2_followup

The first patch brings small coding style improvements to
OvmfPkg/Tcg/Tcg2Config. The second patch trims a superfluous PPI from
SecurityPkg/Tcg/TcgPei's DEPEX.

Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Chao Zhang <chao.b.zhang@intel.com>
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Marc-André Lureau <marcandre.lureau@redhat.com>

Laszlo Ersek (2):
  OvmfPkg/Tcg2ConfigPei: trivial coding style updates
  SecurityPkg/TcgPei: drop PeiReadOnlyVariable from Depex

 OvmfPkg/Tcg/Tcg2Config/Tcg2ConfigPei.inf | 20 +++----
 OvmfPkg/Tcg/Tcg2Config/Tcg2ConfigPeim.c  | 55 +++++++++++---------
 SecurityPkg/Tcg/TcgPei/TcgPei.inf        |  1 -
 3 files changed, 40 insertions(+), 36 deletions(-)

-- 
2.14.1.3.gb7cf6e02401b



             reply	other threads:[~2018-03-09 19:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 20:05 Laszlo Ersek [this message]
2018-03-09 20:05 ` [PATCH 1/2] OvmfPkg/Tcg2ConfigPei: trivial coding style updates Laszlo Ersek
2018-03-09 20:05 ` [PATCH 2/2] SecurityPkg/TcgPei: drop PeiReadOnlyVariable from Depex Laszlo Ersek
2018-03-09 23:12   ` Yao, Jiewen
2018-03-13  1:20   ` Zhang, Chao B
2018-03-09 23:50 ` [PATCH 0/2] OvmfPkg, SecurityPkg: small followup patches after the TPM2 addition to OVMF Jordan Justen
2018-03-10 15:34   ` Laszlo Ersek

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=20180309200525.27376-1-lersek@redhat.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