mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@barebox.org>
Subject: Re: [PATCH RFC 1/2] images: allow suppressing missing firmware stderr output
Date: Mon, 23 Feb 2026 12:20:26 +0100	[thread overview]
Message-ID: <177184562663.223620.3119178404416997287.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260112141746.3068571-1-a.fatoum@barebox.org>


On Mon, 12 Jan 2026 15:17:39 +0100, 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.
> 
> [...]

Applied, thanks!

[1/2] images: allow suppressing missing firmware stderr output
      https://git.pengutronix.de/cgit/barebox/commit/?id=a321c57e369f (link may not be stable)
[2/2] MAKEALL: add a new develop mode option
      https://git.pengutronix.de/cgit/barebox/commit/?id=5f73fd39f914 (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2026-02-23 11:20 UTC|newest]

Thread overview: 4+ 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 ` [PATCH RFC 1/2] images: allow suppressing missing firmware stderr output Ahmad Fatoum
2026-02-23 11:20 ` Sascha Hauer [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=177184562663.223620.3119178404416997287.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@barebox.org \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox