[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130217115555.GA6782@S2101-09.ap.freescale.net>
Date: Sun, 17 Feb 2013 19:55:57 +0800
From: Shawn Guo <shawn.guo@...aro.org>
To: Fabio Estevam <festevam@...il.com>
CC: <davem@...emloft.net>, <s.hauer@...gutronix.de>, <marex@...x.de>,
<netdev@...r.kernel.org>,
Fabio Estevam <fabio.estevam@...escale.com>
Subject: Re: [PATCH 2/2] net: fec: Improve logging
On Sat, Feb 16, 2013 at 08:53:27PM -0200, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@...escale.com>
>
> In case the request of the GPIO reset fails it is interesting to log
> such error even if DEBUG is not enabled, so promote the message to dev_err.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@...escale.com>
> ---
> drivers/net/ethernet/freescale/fec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/freescale/fec.c b/drivers/net/ethernet/freescale/fec.c
> index 5864a67..29d82cf 100644
> --- a/drivers/net/ethernet/freescale/fec.c
> +++ b/drivers/net/ethernet/freescale/fec.c
> @@ -1695,7 +1695,7 @@ static void fec_reset_phy(struct platform_device *pdev)
> err = devm_gpio_request_one(&pdev->dev, phy_reset,
> GPIOF_OUT_INIT_LOW, "phy-reset");
> if (err) {
> - pr_debug("FEC: failed to get gpio phy-reset: %d\n", err);
> + dev_err(&pdev->dev, "failed to get phy-reset-gpios: %d\n", err);
Shouldn't dev_dbg be more like a equivalent of pr_debug? The reason
why it's taken as a debug message rather than an error is that some
board design may not have reset line for phy.
Shawn
> return;
> }
> msleep(msec);
> --
> 1.7.9.5
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists