From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 1/3] ARM: rpi: turn fixup message into debug messages
Date: Wed, 11 Sep 2024 10:17:45 +0200 [thread overview]
Message-ID: <20240911081747.1523613-1-a.fatoum@pengutronix.de> (raw)
When network booted, these properties may be missing and informing the
user about it arguably just clutters the log.
Thus bump down the log level to debug.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
arch/arm/boards/raspberry-pi/rpi-common.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boards/raspberry-pi/rpi-common.c b/arch/arm/boards/raspberry-pi/rpi-common.c
index 628f657ea216..ee0b0f63dbef 100644
--- a/arch/arm/boards/raspberry-pi/rpi-common.c
+++ b/arch/arm/boards/raspberry-pi/rpi-common.c
@@ -301,7 +301,7 @@ static struct device_node *register_vc_fixup(struct device_node *root,
tmp->full_name = xstrdup(ret->full_name);
of_register_fixup(rpi_vc_fdt_fixup, tmp);
} else {
- pr_info("no '%s' node found in vc fdt\n", path);
+ pr_debug("no '%s' node found in vc fdt\n", path);
}
return ret;
@@ -341,7 +341,7 @@ static int register_vc_property_fixup(struct device_node *root,
of_register_fixup(rpi_vc_fdt_fixup_property, fixup_data);
} else {
- pr_info("no '%s' node found in vc fdt\n", path);
+ pr_debug("no '%s' node found in vc fdt\n", path);
return -ENOENT;
}
--
2.39.2
next reply other threads:[~2024-09-11 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 8:17 Ahmad Fatoum [this message]
2024-09-11 8:17 ` [PATCH 2/3] ARM: rpi: always add built-in env Ahmad Fatoum
2024-09-11 8:17 ` [PATCH 3/3] ARM: rpi: return correct error code when failing to read revision Ahmad Fatoum
2024-09-11 8:29 ` [PATCH 1/3] ARM: rpi: turn fixup message into debug messages 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=20240911081747.1523613-1-a.fatoum@pengutronix.de \
--to=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