From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@barebox.org>
Subject: [PATCH 2/4] ARM: at91: sama5d3_xplained: drop invalid hostname
Date: Fri, 6 Nov 2026 12:13:48 +0100 [thread overview]
Message-ID: <20261106111352.3535034-2-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20261106111352.3535034-1-a.fatoum@pengutronix.de>
From: Ahmad Fatoum <a.fatoum@barebox.org>
Host names can't contain underscores, so barebox complains at every
boot:
WARNING: Hostname is not valid, please fix it
Without the override, the hostname is derived from the
"atmel,sama5d3-xplained" compatible instead, which is valid, so let's
drop it.
The net boot entry now looks for *-sama5d3-xplained instead of
*-sama5d3_xplained. This isn't worth a migration guide entry, as
barebox has been warning about the old name since v2024.05.0.
Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
---
arch/arm/boards/sama5d3_xplained/board.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm/boards/sama5d3_xplained/board.c b/arch/arm/boards/sama5d3_xplained/board.c
index 4d908e6b9f62..c6c1105e5eb5 100644
--- a/arch/arm/boards/sama5d3_xplained/board.c
+++ b/arch/arm/boards/sama5d3_xplained/board.c
@@ -39,8 +39,6 @@ static int sama5d3_xplained_probe(struct device *dev)
{
struct clk *clk;
- barebox_set_hostname("sama5d3_xplained");
-
if (IS_ENABLED(CONFIG_DEFAULT_ENVIRONMENT_GENERIC))
defaultenv_append_directory(defaultenv_sama5d3_xplained);
--
2.47.3
next prev parent reply other threads:[~2026-11-06 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 11:13 [PATCH 1/4] ARM: at91: sama5d3: pass BootROM r4 on to barebox proper Ahmad Fatoum
2026-11-06 11:13 ` Ahmad Fatoum [this message]
2026-11-06 11:13 ` [PATCH 3/4] pwm: atmel: look up the clock without a name Ahmad Fatoum
2026-11-06 11:13 ` [PATCH 4/4] ARM: at91: sama5d3: Migrate to MFD-based SMC driver Ahmad Fatoum
2026-11-09 9:52 ` [PATCH 1/4] ARM: at91: sama5d3: pass BootROM r4 on to barebox proper Sascha Hauer
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=20261106111352.3535034-2-a.fatoum@pengutronix.de \
--to=a.fatoum@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