From: Sascha Hauer <sha@pengutronix.de>
To: Johannes Zink <j.zink@pengutronix.de>
Cc: barebox@lists.infradead.org, patchwork-jzi@pengutronix.de
Subject: Re: [PATCH v2] net: phy: print error messages to log
Date: Tue, 9 May 2023 09:21:34 +0200 [thread overview]
Message-ID: <20230509072134.GA29365@pengutronix.de> (raw)
In-Reply-To: <20230509060521.707205-1-j.zink@pengutronix.de>
On Tue, May 09, 2023 at 08:05:21AM +0200, 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 dev_info and dev_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>
> ---
> Changelog:
>
> v1 -> v2: Worked in Ahmad's review findings:
> - use dev_err and dev_info instead of pr_err and pr_info
>
> Thank you for your review!
>
> drivers/net/phy/phy.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied, thanks
Sascha
>
> diff --git a/drivers/net/phy/phy.c b/drivers/net/phy/phy.c
> index 54dbbca7255a..dbc30b66b828 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");
> + dev_err(&edev->dev, "Unable to find a PHY (unknown ID?)\n");
>
> 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"
> + dev_info(&phydev->dev, "PHY remote fault detected\n"
> "PHY restarting auto-negotiation\n");
> phy_write(phydev, MII_BMCR,
> BMCR_ANENABLE | BMCR_ANRESTART);
> --
> 2.39.2
>
>
>
--
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-09 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 6:05 Johannes Zink
2023-05-09 7:21 ` 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=20230509072134.GA29365@pengutronix.de \
--to=sha@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