public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kun Qin" <kuqin12@gmail.com>
To: devel@edk2.groups.io
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Leif Lindholm <quic_llindhol@quicinc.com>,
	Graeme Gregory <graeme@nuviainc.com>,
	Radoslaw Biernacki <rad@semihalf.com>,
	Masami Hiramatsu <masami.hiramatsu@linaro.org>,
	Nhi Pham <nhi@os.amperecomputing.com>,
	Vu Nguyen <vunguyen@os.amperecomputing.com>,
	Thang Nguyen <thang@os.amperecomputing.com>,
	Chuong Tran <chuong@os.amperecomputing.com>,
	Thomas Abraham <thomas.abraham@arm.com>,
	Sami Mujawar <sami.mujawar@arm.com>,
	Abner Chang <abner.chang@hpe.com>,
	Gilbert Chen <gilbert.chen@hpe.com>,
	Daniel Schaefer <daniel.schaefer@hpe.com>,
	Jeremy Linton <jeremy.linton@arm.com>,
	Peng Xie <xiepeng@phytium.com.cn>,
	Ling Jia <jialing@phytium.com.cn>,
	Yiqi Shu <shuyiqi@phytium.com.cn>
Subject: Re: [edk2-devel] [edk2-platforms][PATCH v1 0/7] Resolving SecureBootVariableLib dependency
Date: Fri, 15 Jul 2022 17:34:57 -0700	[thread overview]
Message-ID: <440c3e97-8100-fbbc-b5ee-4d0b9100fd76@gmail.com> (raw)
In-Reply-To: <16FFF67A11C27DF8.12773@groups.io>

Hi SiFive, QEMU, Socionext & Pythium maintainers,

This patch series was sent to resolve the newly introduced dependency in 
the impacted
packages/platforms.

Could you please provide feedback if any? Any input is appreciated.

Regards,
Kun

On 7/8/2022 2:02 PM, Kun Qin via groups.io wrote:
> The new changes in SecureBootVariableLib brought in a new dependency
> of PlatformPKProtectionLib.
>
> This patch series added the new library instance from SecurityPkg to
> resolve edk2 platforms build.
>
> Patch v1 branch:https://github.com/kuqin12/edk2-platforms/tree/fix_sb_dep
>
> Cc: Ard Biesheuvel<ardb+tianocore@kernel.org>
> Cc: Leif Lindholm<quic_llindhol@quicinc.com>
> Cc: Graeme Gregory<graeme@nuviainc.com>
> Cc: Radoslaw Biernacki<rad@semihalf.com>
> Cc: Masami Hiramatsu<masami.hiramatsu@linaro.org>
> Cc: Nhi Pham<nhi@os.amperecomputing.com>
> Cc: Vu Nguyen<vunguyen@os.amperecomputing.com>
> Cc: Thang Nguyen<thang@os.amperecomputing.com>
> Cc: Chuong Tran<chuong@os.amperecomputing.com>
> Cc: Thomas Abraham<thomas.abraham@arm.com>
> Cc: Sami Mujawar<sami.mujawar@arm.com>
> Cc: Abner Chang<abner.chang@hpe.com>
> Cc: Gilbert Chen<gilbert.chen@hpe.com>
> Cc: Daniel Schaefer<daniel.schaefer@hpe.com>
> Cc: Jeremy Linton<jeremy.linton@arm.com>
> Cc: Peng Xie<xiepeng@phytium.com.cn>
> Cc: Ling Jia<jialing@phytium.com.cn>
> Cc: Yiqi Shu<shuyiqi@phytium.com.cn>
>
> Kun Qin (7):
>    RaspberryPi: Pipeline: Resolving newly introduced dependency
>    U5SeriesPkg: Pipeline: Resolving newly introduced dependency
>    VExpressPkg: Pipeline: Resolving newly introduced dependency
>    Qemu: Pipeline: Resolving newly introduced dependency
>    Socionext: Pipeline: Resolving newly introduced dependency
>    AmpereAltraPkg: Pipeline: Resolving newly introduced dependency
>    PhytiumCommonPkg: Pipeline: Resolving newly introduced dependency
>
>   Platform/ARM/VExpressPkg/ArmVExpress.dsc.inc                         | 1 +
>   Platform/Qemu/SbsaQemu/SbsaQemu.dsc                                  | 1 +
>   Platform/RaspberryPi/RPi3/RPi3.dsc                                   | 1 +
>   Platform/RaspberryPi/RPi4/RPi4.dsc                                   | 1 +
>   Platform/SiFive/U5SeriesPkg/FreedomU500VC707Board/U500.dsc           | 1 +
>   Platform/SiFive/U5SeriesPkg/FreedomU540HiFiveUnleashedBoard/U540.dsc | 1 +
>   Platform/Socionext/DeveloperBox/DeveloperBox.dsc                     | 1 +
>   Silicon/Ampere/AmpereAltraPkg/AmpereAltraPkg.dsc.inc                 | 1 +
>   Silicon/Phytium/PhytiumCommonPkg/PhytiumCommonPkg.dsc.inc            | 1 +
>   9 files changed, 9 insertions(+)
>

           reply	other threads:[~2022-07-16  0:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <16FFF67A11C27DF8.12773@groups.io>]

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=440c3e97-8100-fbbc-b5ee-4d0b9100fd76@gmail.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