From: Renaud Barbier <renaud.barbier@ametek.com>
To: barebox@lists.infradead.org
Cc: Renaud Barbier <renaud.barbier@ametek.com>
Subject: [PATCH v2 1/4] net: gianfar: disable link information
Date: Wed, 4 Feb 2026 11:46:18 +0000 [thread overview]
Message-ID: <20260204114621.2130261-2-renaud.barbier@ametek.com> (raw)
In-Reply-To: <20260204114621.2130261-1-renaud.barbier@ametek.com>
Link information are provided by the PHY layer so turn the information
messages into debug messages.
Signed-off-by: Renaud Barbier <renaud.barbier@ametek.com>
---
drivers/net/gianfar.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/net/gianfar.c b/drivers/net/gianfar.c
index 18b3c8849c..d0f606279f 100644
--- a/drivers/net/gianfar.c
+++ b/drivers/net/gianfar.c
@@ -121,11 +121,11 @@ static void gfar_adjust_link(struct eth_device *edev)
out_be32(regs + GFAR_ECNTRL_OFFSET, ecntrl);
out_be32(regs + GFAR_MACCFG2_OFFSET, maccfg2);
- dev_info(&edev->dev, "Speed: %d, %s duplex\n", priv->speed,
- (priv->duplexity) ? "full" : "half");
+ dev_dbg(&edev->dev, "Speed: %d, %s duplex\n", priv->speed,
+ (priv->duplexity) ? "full" : "half");
} else {
- dev_info(&edev->dev, "No link.\n");
+ dev_dbg(&edev->dev, "No link.\n");
}
}
--
2.43.0
next prev parent reply other threads:[~2026-02-04 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 11:46 [PATCH v2 0/4] net: expand gianfar support to ls1021a Renaud Barbier
2026-02-04 11:46 ` Renaud Barbier [this message]
2026-02-04 11:46 ` [PATCH v2 2/4] gianfar: apply checkpatch recommendations Renaud Barbier
2026-02-04 11:46 ` [PATCH v2 3/4] net:gianfar: add device tree support Renaud Barbier
2026-02-04 11:46 ` [PATCH v2 4/4] ARM: ls1021a: initial Ethernet and mdio configuration Renaud Barbier
2026-02-09 14:43 ` Sascha Hauer
2026-02-09 17:46 ` Renaud Barbier
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=20260204114621.2130261-2-renaud.barbier@ametek.com \
--to=renaud.barbier@ametek.com \
--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