From: Andreas Schwab <schwab@linux-m68k.org>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Daniel Kiper <dkiper@net-space.pl>,
Andrei Borzenkov <arvidjaar@gmail.com>,
Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>,
Nikita Ermakov <arei@altlinux.org>,
Ard Biesheuvel <ard.biesheuvel@arm.com>,
Atish Patra <Atish.Patra@wdc.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
GRUB development mailing list <grub-devel@gnu.org>
Subject: Re: [PATCH 0/2] efinet: correct closing of SNP protocol
Date: Wed, 06 Oct 2021 16:28:51 +0200 [thread overview]
Message-ID: <87ee8yb524.fsf@igel.home> (raw)
In-Reply-To: <20211006083043.9313-1-heinrich.schuchardt@canonical.com> (Heinrich Schuchardt's message of "Wed, 6 Oct 2021 10:30:41 +0200")
On Okt 06 2021, Heinrich Schuchardt wrote:
> In the context of the implementation of the EFI_LOAD_FILE2_PROTOCOL for
> the initial ramdisk it was observed that opening the SNP protocol failed
> (https://lists.gnu.org/archive/html/grub-devel/2021-10/msg00020.html).
> This is due to an incorrect call to CloseProtocol().
>
> This is corrected in the first patch.
>
> The second patch provides a new function grub_efi_close_protocol() to
> simplify the coding.
Sucessfully tested with
https://download.opensuse.org/ports/riscv/tumbleweed/iso/openSUSE-Tumbleweed-NET-riscv64-Media.iso
on the Hifive Unmatched.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2021-10-06 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 8:30 [PATCH 0/2] efinet: correct closing of SNP protocol Heinrich Schuchardt
2021-10-06 8:30 ` [PATCH 1/2] " Heinrich Schuchardt
2021-11-23 17:52 ` Daniel Kiper
2021-10-06 8:30 ` [PATCH 2/2] efi: library function grub_efi_close_protocol() Heinrich Schuchardt
2021-11-23 17:59 ` Daniel Kiper
2021-10-06 14:28 ` Andreas Schwab [this message]
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-all 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=87ee8yb524.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=Atish.Patra@wdc.com \
--cc=ard.biesheuvel@arm.com \
--cc=arei@altlinux.org \
--cc=arvidjaar@gmail.com \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=leif.lindholm@linaro.org \
--cc=phcoder@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.