From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Johannes Zink <j.zink@pengutronix.de>, barebox@lists.infradead.org
Cc: patchwork-jzi@pengutronix.de
Subject: Re: [PATCH v1] net: phy: print error messages to log
Date: Mon, 8 May 2023 16:00:38 +0200 [thread overview]
Message-ID: <631a0067-9553-c6a8-d015-c3e9371d9b3b@pengutronix.de> (raw)
In-Reply-To: <20230508133510.188016-1-j.zink@pengutronix.de>
Hello Johannes,
On 08.05.23 15:35, Johannes Zink wrote:
> Previously the phy core did just print info and error messages to
> console, but they did not show up in the system log.
>
> Now the pr_info and pr_err macros are used instead of raw puts,
> they are now nicely formatted and show up in the log.
>
> Signed-off-by: Johannes Zink <j.zink@pengutronix.de>
Thanks for your patch.
> ---
> drivers/net/phy/phy.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/phy/phy.c b/drivers/net/phy/phy.c
> index 54dbbca7255a..64e7e33254e2 100644
> --- a/drivers/net/phy/phy.c
> +++ b/drivers/net/phy/phy.c
> @@ -462,7 +462,7 @@ int phy_device_connect(struct eth_device *edev, struct mii_bus *bus, int addr,
> ret = -ENODEV;
> out:
> if (ret)
> - puts("Unable to find a PHY (unknown ID?)\n");
> + pr_err("Unable to find a PHY (unknown ID?)\n");
Please use dev_err(&edev->dev, instead
>
> return ret;
> }
> @@ -675,7 +675,7 @@ int genphy_aneg_done(struct phy_device *phydev)
>
> /* Restart auto-negotiation if remote fault */
> if (bmsr & BMSR_RFAULT) {
> - puts("PHY remote fault detected\n"
> + pr_info("PHY remote fault detected\n"
> "PHY restarting auto-negotiation\n");
Likewise, dev_info(&phydev->dev,
> phy_write(phydev, MII_BMCR,
> BMCR_ANENABLE | BMCR_ANRESTART);
Thanks,
Ahmad
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-05-08 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 13:35 Johannes Zink
2023-05-08 14:00 ` Ahmad Fatoum [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=631a0067-9553-c6a8-d015-c3e9371d9b3b@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=j.zink@pengutronix.de \
--cc=patchwork-jzi@pengutronix.de \
/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