public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Dusty Mabe <dusty@dustymabe.com>
To: git-commits@fedoraproject.org
Subject: [rpms/uboot-tools] rawhide: FFL: convert a few debug statements into info
Date: Tue, 23 Jun 2026 09:22:36 GMT [thread overview]
Message-ID: <178220655623.1.8328122984946855135.rpms-uboot-tools-40a137ae166c@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/uboot-tools
Branch : rawhide
Commit : 40a137ae166cd4a38133cf8bb4be8b012be721e6
Author : Dusty Mabe <dusty@dustymabe.com>
Date : 2026-06-19T14:20:29-04:00
Stats : +2/-2 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/uboot-tools/c/40a137ae166cd4a38133cf8bb4be8b012be721e6?branch=rawhide
Log:
FFL: convert a few debug statements into info
This way on boot we'll get one of the three:
- Found DTB on disk
- Found DTB: Prior firmware
- Using DT from U-Boot
Since it's only one log statement per boot I don't think this will
add too much noise.
---
diff --git a/uefi-initial-find_fdt_location-for-finding-the-DT-on-disk.patch b/uefi-initial-find_fdt_location-for-finding-the-DT-on-disk.patch
index 5948f93..ac58bad 100644
--- a/uefi-initial-find_fdt_location-for-finding-the-DT-on-disk.patch
+++ b/uefi-initial-find_fdt_location-for-finding-the-DT-on-disk.patch
@@ -169,7 +169,7 @@ index 44b806aadc4..61e982091b9 100644
+ /* Check if there is device tree loaded from disk */
+ fdt_opt = find_fdt_location();
+ if (fdt_opt)
-+ log_debug("Found DTB on disk\n");
++ log_info("Found DTB on disk\n");
+
/* Check if there is a hardware device tree */
- fdt_opt = env_get("fdt_addr");
@@ -181,7 +181,7 @@ index 44b806aadc4..61e982091b9 100644
/* Use our own device tree as fallback */
if (!fdt_opt) {
fdt_opt = env_get("fdtcontroladdr");
-+ log_debug("Using DT from U-Boot\n");
++ log_info("Using DT from U-Boot\n");
if (!fdt_opt) {
log_err("need device tree\n");
return EFI_NOT_FOUND;
reply other threads:[~2026-06-23 9:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178220655623.1.8328122984946855135.rpms-uboot-tools-40a137ae166c@fedoraproject.org \
--to=dusty@dustymabe.com \
--cc=git-commits@fedoraproject.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