mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@barebox.org>
To: BAREBOX <barebox@lists.infradead.org>,
	Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH RFC 1/2] images: allow suppressing missing firmware stderr output
Date: Mon, 9 Feb 2026 13:36:22 +0100	[thread overview]
Message-ID: <3110bd2d-0b62-458f-90df-c8b9e79e721b@barebox.org> (raw)
In-Reply-To: <20260112141746.3068571-1-a.fatoum@barebox.org>

Hello Sascha,

On 1/12/26 3:17 PM, Ahmad Fatoum wrote:
> There is a Kconfig option to turn missing firmware to an error, but
> there is no way to suppress the warning that is printed in any case.
> 
> Suppressing the warning is useful however when reproducing an issue with
> a multi_defconfig, so allow changing it to output to stdout by means of
> an environment variable.
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>

Any thoughts on this?

Cheers,
Ahmad

> ---
>  images/Makefile | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/images/Makefile b/images/Makefile
> index ebbf57b46355..96f66b0a8e70 100644
> --- a/images/Makefile
> +++ b/images/Makefile
> @@ -254,7 +254,8 @@ images: $(image-y-path) $(flash-link) $(flash-list) $(symlink-y-path) FORCE
>  	@echo "images built:"
>  	@for i in $(image-y); do \
>  	  if [ -s $(obj)/$$i ]; then echo $$i; \
> -	  else >&2 echo "** $$i skipped due to missing firmware **"; \
> +	  else $(if $(NO_MISSING_FIRMWARE_WARNING),,>&2) \
> +	  	echo "** $$i skipped due to missing firmware **"; \
>  	  $(if $(CONFIG_MISSING_FIRMWARE_ERROR), >&2 sed 's/^/\t/' <$(obj)/$${i}.missing-firmware; missing=1;) \
>  	  fi; done; if [ -n "$$missing" ]; then \
>  	    echo >&2 "Firmware missing in CONFIG_MISSING_FIRMWARE_ERROR=y build"; exit 1; fi




      parent reply	other threads:[~2026-02-09 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 14:17 Ahmad Fatoum
2026-01-12 14:17 ` [PATCH RFC 2/2] MAKEALL: add a new develop mode option Ahmad Fatoum
2026-02-09 12:36 ` Ahmad Fatoum [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=3110bd2d-0b62-458f-90df-c8b9e79e721b@barebox.org \
    --to=a.fatoum@barebox.org \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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