From: "Ojeda Leon, Nicolas" <ncoleon@amazon.com>
To: <devel@edk2.groups.io>
Cc: <graf@amazon.com>, <quic_llindhol@quicinc.com>,
<sami.mujawar@arm.com>, <brijesh.singh@amd.com>,
<erdemaktas@google.com>, <jejb@linux.ibm.com>,
<min.m.xu@intel.com>, <thomas.lendacky@amd.com>,
<rebecca@bsdio.com>, <grehan@freebsd.org>,
<sebastien.boeuf@intel.com>, <anthony.perard@citrix.com>,
<julien@xen.org>, <ardb+tianocore@kernel.org>,
<jiewen.yao@intel.com>, <jordan.l.justen@intel.com>,
<kraxel@redhat.com>, Nicolas Ojeda Leon <ncoleon@amazon.com>
Subject: [PATCH 0/2] Include HardwareInfoLib in all platforms using
Date: Thu, 23 Jun 2022 17:22:09 +0200 [thread overview]
Message-ID: <cover.1655996741.git.ncoleon@amazon.com> (raw)
In past days, a patch series to support multiple PCI host bridges in Ovmf
was merged which caused an error in ArmVirtQemuKernel.dsc build, part
of the CI pipeline.
These 2 commits aim at fixing this issue by adding the HardwareInfoLib
to all ArmVirt* platofrms as well as for IntelTdx which were missing
this library that now is a dependency of PciHostBridgeUtilityLib.
Nicolas Ojeda Leon (2):
ArmVirtPkg: Include DxeHardwareInfoLib library class in dsc
Ovmf: Include HardwareInfoLib library classes for IntelTdx
ArmVirtPkg/ArmVirt.dsc.inc | 1 +
ArmVirtPkg/ArmVirtQemu.dsc | 1 -
OvmfPkg/IntelTdx/IntelTdxX64.dsc | 2 ++
3 files changed, 3 insertions(+), 1 deletion(-)
--
2.17.1
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
next reply other threads:[~2022-06-23 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 15:22 Ojeda Leon, Nicolas [this message]
2022-06-23 15:23 ` [PATCH 1/2] ArmVirtPkg: Include DxeHardwareInfoLib library class in dsc Ojeda Leon, Nicolas
2022-06-24 18:07 ` [PATCH 0/2] Include HardwareInfoLib in all platforms using Ard Biesheuvel
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=cover.1655996741.git.ncoleon@amazon.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