public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Vincent Stehlé" <vincent.stehle@arm.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Tom Rini <trini@konsulko.com>,
	u-boot@lists.denx.de
Subject: Re: [PATCH 1/4] lib: uuid: add EBBR 2.1 conformance profile GUID
Date: Mon, 9 Mar 2026 15:38:10 +0100	[thread overview]
Message-ID: <aa7bUobdKM7AOd_h@debian> (raw)
In-Reply-To: <3d35df48-0669-4c0c-a770-86bfa6b65d79@gmx.de>

On Mon, Mar 09, 2026 at 01:19:32PM +0100, Heinrich Schuchardt wrote:

Hi Heinrich,

Thanks for your review; I will modify as per your suggestion and send a v2.

Best regards,
Vincent.

> On 3/5/26 17:13, Vincent Stehlé wrote:
> > Add support for printing the EFI_CONFORMANCE_PROFILE_EBBR_2_1_GUID as human
> > readable text.
> > 
> > This is added in the GUIDs range, which is compiled in only when
> > CONFIG_CMD_EFIDEBUG is set.
> > 
> > Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>
> > Cc: Tom Rini <trini@konsulko.com>
> > ---
> >   lib/uuid.c | 4 ++++
> >   1 file changed, 4 insertions(+)
> > 
> > diff --git a/lib/uuid.c b/lib/uuid.c
> > index 0a166320e07..d9d5414d4bf 100644
> > --- a/lib/uuid.c
> > +++ b/lib/uuid.c
> > @@ -254,6 +254,10 @@ static const struct {
> >   		NULL, "EFI Conformance Profiles Table",
> >   		EFI_CONFORMANCE_PROFILES_TABLE_GUID,
> >   	},
> 
> Some boards have tight binary size restrictions.
> 
> If CONFIG_EFI_ECPT=n, we don't need the GUID text. I would suggest to hide
> it behind an #ifdef.
> 
> Best regards
> 
> Heinrich
> 
> > +	{
> > +		NULL, "EFI EBBR 2.1 Conformance Profile",
> > +		EFI_CONFORMANCE_PROFILE_EBBR_2_1_GUID,
> > +	},
> >   #ifdef CONFIG_EFI_RISCV_BOOT_PROTOCOL
> >   	{
> >   		NULL, "RISC-V Boot",
> 

  reply	other threads:[~2026-03-09 14:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 16:13 [PATCH 0/4] Add an efidebug ecpt command Vincent Stehlé
2026-03-05 16:13 ` [PATCH 1/4] lib: uuid: add EBBR 2.1 conformance profile GUID Vincent Stehlé
2026-03-09 12:19   ` Heinrich Schuchardt
2026-03-09 14:38     ` Vincent Stehlé [this message]
2026-03-05 16:13 ` [PATCH 2/4] efi_loader: export efi_ecpt_guid Vincent Stehlé
2026-03-09 12:26   ` Heinrich Schuchardt
2026-03-05 16:13 ` [PATCH 3/4] cmd: efidebug: add ecpt command Vincent Stehlé
2026-03-09 12:23   ` Heinrich Schuchardt
2026-03-09 15:02     ` Vincent Stehlé
2026-03-05 16:13 ` [PATCH 4/4] test/py: add ECPT tests Vincent Stehlé
2026-03-09 12:37   ` Heinrich Schuchardt
2026-03-09 16:36 ` [PATCH v2 1/4] lib: uuid: add EBBR 2.1 conformance profile GUID Vincent Stehlé
2026-03-09 16:38   ` Heinrich Schuchardt
2026-03-11 16:14   ` Ilias Apalodimas
2026-03-09 16:36 ` [PATCH v2 2/4] efi_loader: export efi_ecpt_guid Vincent Stehlé
2026-03-09 16:40   ` Heinrich Schuchardt
2026-03-09 17:34     ` Vincent Stehlé
2026-03-11 16:24   ` Ilias Apalodimas
2026-03-09 16:36 ` [PATCH v2 3/4] cmd: efidebug: add ecpt command Vincent Stehlé
2026-03-09 16:41   ` Heinrich Schuchardt
2026-03-11 16:20   ` Ilias Apalodimas
2026-03-09 16:36 ` [PATCH v2 4/4] test/py: add ECPT tests Vincent Stehlé

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=aa7bUobdKM7AOd_h@debian \
    --to=vincent.stehle@arm.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox