From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH] bootm: include origin of device tree in verbose output
Date: Mon, 29 Jun 2026 12:27:24 +0200 [thread overview]
Message-ID: <178272884436.188629.10344130788468648956.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260624060648.1845974-1-a.fatoum@pengutronix.de>
On Wed, 24 Jun 2026 08:06:47 +0200, Ahmad Fatoum wrote:
> To make it easier to see at a glance if the device tree to be passed to
> Linux is barebox' own or an externally provided DT, include this
> information into verbosity level 1.
>
> Previously we only printed "using internal devicetree" at verbosity
> level 2, but that's the same level we dump the whole DT, so we bump it
> down a level and rename it to make it clear what the DT is internal to
> (e.g. it's not a FIT-internal DT).
>
> [...]
Applied, thanks!
[1/1] bootm: include origin of device tree in verbose output
https://git.pengutronix.de/cgit/barebox/commit/?id=5f8f67f08dcf (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-06-29 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 6:06 Ahmad Fatoum
2026-06-29 10:27 ` 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=178272884436.188629.10344130788468648956.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--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