All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Tom Rini <trini@konsulko.com>,
	Patrick Delaunay <patrick.delaunay@foss.st.com>,
	 U-Boot Mailing List <u-boot@lists.denx.de>,
	Sunil V L <sunilvl@ventanamicro.com>
Subject: Re: [PATCH 1/1] lib: allow printing RISC-V EFI Boot Protocol GUID
Date: Sat, 29 Jan 2022 14:09:44 -0700	[thread overview]
Message-ID: <CAPnjgZ0ciEm5Z8fBUd2to0GOeECWAr2mPeg81d71PmO-guk4=g@mail.gmail.com> (raw)
In-Reply-To: <20220128184211.160575-1-heinrich.schuchardt@canonical.com>

Hi Heinrich,

On Fri, 28 Jan 2022 at 11:42, Heinrich Schuchardt
<heinrich.schuchardt@canonical.com> wrote:
>
> On RISC-V a new UEFI protocol has been introduced. Support printing
> its GUID using %pUs.
>
> Cc: Sunil V L <sunilvl@ventanamicro.com>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> ---
> cf.
> [RFC PATCH V2 1/2] efi_loader: Enable RISCV_EFI_BOOT_PROTOCOL support
> https://lists.denx.de/pipermail/u-boot/2022-January/473505.html
> ---
>  lib/uuid.c | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> diff --git a/lib/uuid.c b/lib/uuid.c
> index 24571ef5fb..284f8113ff 100644
> --- a/lib/uuid.c
> +++ b/lib/uuid.c
> @@ -220,7 +220,13 @@ static const struct {
>                 "TCG2 Final Events Table",
>                 EFI_TCG2_FINAL_EVENTS_TABLE_GUID,
>         },
> +#ifdef CONFIG_EFI_RISCV_BOOT_PROTOCOL
> +       {
> +               "RISC-V Boot",
> +               RISCV_EFI_BOOT_PROTOCOL_GUID,
> +       },
>  #endif
> +#endif /* CONFIG_CMD_EFIDEBUG */
>  #ifdef CONFIG_CMD_NVEDIT_EFI
>         /* signature database */
>         {
> --
> 2.33.1
>

Why the #ifdef?

Regards,
Simon

  reply	other threads:[~2022-01-29 21:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 18:42 [PATCH 1/1] lib: allow printing RISC-V EFI Boot Protocol GUID Heinrich Schuchardt
2022-01-29 21:09 ` Simon Glass [this message]
2022-01-29 21:40   ` Heinrich Schuchardt
2022-01-30 23:14     ` Simon Glass
2022-01-31  6:18       ` Heinrich Schuchardt
2022-01-31 16:13         ` Simon Glass

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='CAPnjgZ0ciEm5Z8fBUd2to0GOeECWAr2mPeg81d71PmO-guk4=g@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=patrick.delaunay@foss.st.com \
    --cc=sunilvl@ventanamicro.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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.