From: "Nickle Wang" <nicklew@nvidia.com>
To: <devel@edk2.groups.io>
Cc: Abner Chang <abner.chang@amd.com>, Igor Kulchytskyy <igork@ami.com>
Subject: [edk2-redfish-client][PATCH 0/9] Fix RedfishClientPkg build errors
Date: Mon, 5 Jun 2023 21:48:47 +0800 [thread overview]
Message-ID: <20230605134847.25056-1-nicklew@nvidia.com> (raw)
Fix RedfishClientPkg build errors and typos. The compiler toolchain is GCC5.
Signed-off-by: Nickle Wang <nicklew@nvidia.com>
Cc: Abner Chang <abner.chang@amd.com>
Cc: Igor Kulchytskyy <igork@ami.com>
Nickle Wang (9):
RedfishClientPkg/ConverterLib: Fix unused-but-set-variable error
RedfishClientPkg/RedfishAddendumLib: Fix build error
RedfishClientPkg/EdkIIRedfishResourceConfigLib: Fix build error
RedfishClientPkg/RedfishFeatureUtilityLib: Fix build error
RedfishClientPkg/RedfishETagDxe: Fix build error
RedfishClientPkg/RedfishConfigLangMapDxe: Fix build error
RedfishClientPkg/BiosDxe: Fix build error
RedfishClientPkg/MemoryDxe: Fix build error
RedfishClientPkg/ComputerSystemDxe: Fix build error
.../Protocol/EdkIIRedfishETagProtocol.h | 2 +-
.../src/Bios/Bios.V1_0_9/Bios.V1_0_9.c | 7 +-
.../ComputerSystem.V1_5_0.c | 298 ++++++++----------
.../ComputerSystemCollection.c | 22 +-
.../src/Memory/Memory.V1_7_1/Memory.V1_7_1.c | 207 ++++++------
.../MemoryCollection/MemoryCollection.c | 22 +-
.../Features/Bios/v1_0_9/Dxe/BiosDxe.c | 20 +-
.../v1_5_0/Dxe/ComputerSystemDxe.c | 19 +-
.../Features/Memory/V1_7_1/Dxe/MemoryDxe.c | 19 +-
.../EdkIIRedfishResourceConfigLib.c | 4 +-
.../RedfishAddendumLib/RedfishAddendumLib.c | 4 +-
.../RedfishFeatureUtilityLib.c | 50 +--
.../RedfishConfigLangMapDxe.c | 3 +
.../RedfishETagDxe/RedfishETagDxe.c | 13 +-
14 files changed, 326 insertions(+), 364 deletions(-)
--
2.17.1
reply other threads:[~2023-06-05 13:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230605134847.25056-1-nicklew@nvidia.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