All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Linus Walleij <linusw@kernel.org>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Kory Maincent <kory.maincent@bootlin.com>,
	u-boot@lists.u-boot-project.org
Subject: Re: [PATCH 1/1] tools: build mkeficapsule for CONFIG_EFI_HAVE_CAPSULE_SUPPORT=y
Date: Thu, 20 Aug 2026 08:55:02 -0600	[thread overview]
Message-ID: <20260820145502.GH523975@bill-the-cat> (raw)
In-Reply-To: <20260820072645.9884-1-heinrich.schuchardt@canonical.com>

[-- Attachment #1: Type: text/plain, Size: 740 bytes --]

On Thu, Aug 20, 2026 at 09:26:45AM +0200, Heinrich Schuchardt wrote:

> Currently we build mkeficapsule by default even if we don't have EFI
> capsule support enabled. This adds a host GnuTLS build dependency.
> 
> Only build mkeficapsule by default if CONFIG_EFI_HAVE_CAPSULE_SUPPORT=y.
> 
> tools-only_defconfig explicitly selects CONFIG_TOOLS_MKEFICAPSULE=y.
> Hence distro packages like Debian's u-boot-tools will still contain
> mkeficapsule.
> 
> Reported-by: Linus Walleij <linusw@kernel.org>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>

This should address the similar type problems other people and platforms
have reported too.

Reviewed-by: Tom Rini <trini@konsulko.com>

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2026-08-20 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20  7:26 [PATCH 1/1] tools: build mkeficapsule for CONFIG_EFI_HAVE_CAPSULE_SUPPORT=y Heinrich Schuchardt
2026-08-20 13:21 ` Linus Walleij
2026-08-20 14:55 ` Tom Rini [this message]
2026-08-20 15:02 ` Kory Maincent

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=20260820145502.GH523975@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=kory.maincent@bootlin.com \
    --cc=linusw@kernel.org \
    --cc=u-boot@lists.u-boot-project.org \
    /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.