From: "Nickle Wang via groups.io" <nicklew=nvidia.com@groups.io>
To: <devel@edk2.groups.io>
Cc: Abner Chang <abner.chang@amd.com>,
Igor Kulchytskyy <igork@ami.com>,
"Nick Ramirez" <nramirez@nvidia.com>
Subject: [edk2-devel] [edk2-redfish-client][PATCH 0/2] introduce Redfish override protocol
Date: Thu, 2 Nov 2023 18:17:40 +0800 [thread overview]
Message-ID: <20231102101740.13707-1-nicklew@nvidia.com> (raw)
Introduce Redfish override protocol. If platform likes to do specific operation
before system reboot, platform implement this protocol and Redfish feature core
driver will call it to notify platform that system is going to reboot. Platform
can reject system reboot by returning error status based on platform policy. This
protocol can be extneded to support more platform notifications in the future.
Signed-off-by: Nickle Wang <nicklew@nvidia.com>
Cc: Abner Chang <abner.chang@amd.com>
Cc: Igor Kulchytskyy <igork@ami.com>
Cc: Nick Ramirez <nramirez@nvidia.com>
Nickle Wang (2):
RedfishClientPkg: introduce Redfish override protocol
RedfishClientPkg/RedfishFeatureCoreDxe: notify platform before reboot.
RedfishClientPkg/RedfishClientPkg.dec | 2 +
.../RedfishFeatureCoreDxe.inf | 1 +
.../Protocol/EdkIIRedfishOverrideProtocol.h | 60 +++++++++++++++++++
.../RedfishFeatureCoreDxe.h | 1 +
.../RedfishFeatureCoreDxe.c | 25 +++++++-
5 files changed, 87 insertions(+), 2 deletions(-)
create mode 100644 RedfishClientPkg/Include/Protocol/EdkIIRedfishOverrideProtocol.h
--
2.17.1
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#110511): https://edk2.groups.io/g/devel/message/110511
Mute This Topic: https://groups.io/mt/102338706/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
reply other threads:[~2023-11-02 10:18 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=20231102101740.13707-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