public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Daniel Schaefer" <daniel.schaefer@hpe.com>
To: <devel@edk2.groups.io>
Cc: Daniel Schaefer <daniel.schaefer@hpe.com>,
	Abner Chang <abner.chang@hpe.com>,
	Leif Lindholm <leif@nuviainc.com>
Subject: [PATCH 0/1] Silicon/SiFive: Handle case of NULL FirmwareContext
Date: Wed, 30 Sep 2020 16:50:04 +0800	[thread overview]
Message-ID: <20200930085005.27148-1-daniel.schaefer@hpe.com> (raw)

This is a replacement patch of Abner's with title
  ProcessorPkg/RiscVEdk2SbiLib: Error handling for locating firmware context

I realized that the error handling wasn't bad but unnecessary. Those
funtions can never return an error, since the SBI call they use also
doesn't.

Tested by booting to UEFI Shell. No new error message logged or ASSERT
triggered.

Cc: Abner Chang <abner.chang@hpe.com>
Cc: Leif Lindholm <leif@nuviainc.com>

Daniel Schaefer (1):
  Silicon/SiFive: Handle case of NULL FirmwareContext

 .../Include/Library/RiscVEdk2SbiLib.h         | 12 ++---
 .../PlatformPkg/Universal/Sec/SecMain.c       | 11 +++--
 .../Library/RiscVEdk2SbiLib/RiscVEdk2SbiLib.c | 46 +++++++------------
 .../Library/PeiCoreInfoHobLib/CoreInfoHob.c   | 13 ++++--
 4 files changed, 36 insertions(+), 46 deletions(-)

-- 
2.28.0


             reply	other threads:[~2020-09-30  8:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30  8:50 Daniel Schaefer [this message]
2020-09-30  8:50 ` [PATCH 1/1] Silicon/SiFive: Handle case of NULL FirmwareContext Daniel Schaefer
2020-09-30 13:37   ` Abner Chang
     [not found]   ` <1639933E5766B4C0.8589@groups.io>
2020-10-02  2:40     ` [edk2-devel] " Abner Chang

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=20200930085005.27148-1-daniel.schaefer@hpe.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