public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "Douglas Flick [MSFT]" <doug.edk2@gmail.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kumar, Rahul R" <rahul.r.kumar@intel.com>
Subject: Re: [edk2-devel] [PATCH 0/3] DxeTpm and DxeTpm2MeasureBootLib symbol rename
Date: Thu, 18 Jan 2024 02:28:23 +0000	[thread overview]
Message-ID: <MW4PR11MB587252CC3B957AE21D3606AF8C712@MW4PR11MB5872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <cover.1705529990.git.doug.edk2@gmail.com>

Thank you Doug for the prompt response.

Reviewed-by: Jiewen Yao <Jiewen.yao@intel.com>

> -----Original Message-----
> From: Douglas Flick [MSFT] <doug.edk2@gmail.com>
> Sent: Thursday, January 18, 2024 6:47 AM
> To: devel@edk2.groups.io
> Cc: Douglas Flick [MSFT] <doug.edk2@gmail.com>; Yao, Jiewen
> <jiewen.yao@intel.com>; Kumar, Rahul R <rahul.r.kumar@intel.com>
> Subject: [PATCH 0/3] DxeTpm and DxeTpm2MeasureBootLib symbol rename
> 
> OVMF is failing because it includes both DxeTpm2MeasureBootLib and
> DxeTpm2MeasureBootLib which makes the symbols collide. This patch
> renames the function names to be unique to avoid symbol collision.
> 
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Rahul Kumar <rahul1.kumar@intel.com>
> 
> Signed-off-by: Doug Flick [MSFT] <doug.edk2@gmail.com>
> 
> Douglas Flick [MSFT] (3):
>   SecurityPkg: DxeTpm2MeasureBootLib: SECURITY PATCH 4117/4118 symbol
>     rename
>   SecurityPkg: DxeTpmMeasureBootLib: SECURITY PATCH 4117/4118 symbol
>     rename
>   SecurityPkg: : Updating SecurityFixes.yaml after symbol rename
> 
>  .../DxeTpm2MeasureBootLibSanitization.h       |  8 +++---
>  .../DxeTpmMeasureBootLibSanitization.h        |  8 +++---
>  .../DxeTpm2MeasureBootLib.c                   |  8 +++---
>  .../DxeTpm2MeasureBootLibSanitization.c       |  8 +++---
>  .../DxeTpm2MeasureBootLibSanitizationTest.c   | 26 ++++++++---------
>  .../DxeTpmMeasureBootLib.c                    |  8 +++---
>  .../DxeTpmMeasureBootLibSanitization.c        | 10 +++----
>  .../DxeTpmMeasureBootLibSanitizationTest.c    | 26 ++++++++---------
>  SecurityPkg/SecurityFixes.yaml                | 28 +++++++++++--------
>  9 files changed, 68 insertions(+), 62 deletions(-)
> 
> --
> 2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#113980): https://edk2.groups.io/g/devel/message/113980
Mute This Topic: https://groups.io/mt/103797461/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  parent reply	other threads:[~2024-01-18  2:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 22:47 [edk2-devel] [PATCH 0/3] DxeTpm and DxeTpm2MeasureBootLib symbol rename Doug Flick via groups.io
2024-01-17 22:47 ` [edk2-devel] [PATCH 1/3] SecurityPkg: DxeTpm2MeasureBootLib: SECURITY PATCH 4117/4118 " Doug Flick via groups.io
2024-01-17 22:47 ` [edk2-devel] [PATCH 2/3] SecurityPkg: DxeTpmMeasureBootLib: " Doug Flick via groups.io
2024-01-17 22:47 ` [edk2-devel] [PATCH 3/3] SecurityPkg: : Updating SecurityFixes.yaml after " Doug Flick via groups.io
2024-01-18  2:28 ` Yao, Jiewen [this message]
2024-01-18 20:29 ` [edk2-devel] [PATCH 0/3] DxeTpm and DxeTpm2MeasureBootLib " 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=MW4PR11MB587252CC3B957AE21D3606AF8C712@MW4PR11MB5872.namprd11.prod.outlook.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