From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@barebox.org>
Subject: Re: [PATCH] state: suppress state overwrite warning for barebox DT
Date: Mon, 13 Apr 2026 13:22:58 +0200 [thread overview]
Message-ID: <177607937866.3539112.575697123949531227.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260413100243.1456951-1-a.fatoum@barebox.org>
On Mon, 13 Apr 2026 12:02:43 +0200, Ahmad Fatoum wrote:
> Nowadays, the root != of_get_root_node() check always evaluates to true,
> because fixups are never applied onto the barebox live tree directly,
> but at a copy. This was necessary to allow repeated fixups, e.g. by
> of_diff - + or with multiple boot targets.
>
> The check was useful to have though to differentiate between the case
> that the barebox DT is passed to Linux (where it's benign that the state
> node is overwritten) or the Linux DT having a state node (which can
> mislead as the kernel will be overwritten).
>
> [...]
Applied, thanks!
[1/1] state: suppress state overwrite warning for barebox DT
https://git.pengutronix.de/cgit/barebox/commit/?id=40e7f324b675 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-04-13 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 10:02 Ahmad Fatoum
2026-04-13 11:22 ` 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=177607937866.3539112.575697123949531227.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