From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: mfe@pengutronix.de
Subject: Re: [PATCH 1/3] firmware: support optional firmware in barebox proper
Date: Mon, 06 May 2024 08:32:35 +0200 [thread overview]
Message-ID: <171497715519.331591.620226712013489169.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240503103230.1367842-1-a.fatoum@pengutronix.de>
On Fri, 03 May 2024 12:32:28 +0200, Ahmad Fatoum wrote:
> For firmware used in the prebootloader, missing firmware is handled
> according to the CONFIG_MISSING_FIRMWARE_ERROR symbol:
>
> - If set, barebox will throw an error when assmebling the final image
> with a list of missing firmware
>
> - If unset, a warning will be printed for each barebox image that
> can't be built due to missing firmware and all
>
> [...]
Applied, thanks!
[1/3] firmware: support optional firmware in barebox proper
https://git.pengutronix.de/cgit/barebox/commit/?id=bd29a3aa7e2a (link may not be stable)
[2/3] ARM: layerscape: add helpful runtime warning when firmware is missing
https://git.pengutronix.de/cgit/barebox/commit/?id=9e436059695a (link may not be stable)
[3/3] ci: test: remove generation of dummy firmware
https://git.pengutronix.de/cgit/barebox/commit/?id=8dc8635d90cb (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-05-06 6:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 10:32 Ahmad Fatoum
2024-05-03 10:32 ` [PATCH 2/3] ARM: layerscape: add helpful runtime warning when firmware is missing Ahmad Fatoum
2024-05-06 6:33 ` Sascha Hauer
2024-05-03 10:32 ` [PATCH 3/3] ci: test: remove generation of dummy firmware Ahmad Fatoum
2024-05-06 6:32 ` 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=171497715519.331591.620226712013489169.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=mfe@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