mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Elder <elder@ieee.org>
To: Wang Wenhu <wenhu.wang@vivo.com>,
	davem@davemloft.net, elder@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: kernel@vivo.com
Subject: Re: [PATCH] drivers: ipa: print dev_err info accurately
Date: Mon, 25 May 2020 19:49:25 -0500	[thread overview]
Message-ID: <75dd9de2-c8a8-945a-fb14-26c3c6044bb6@ieee.org> (raw)
In-Reply-To: <20200525062951.29472-1-wenhu.wang@vivo.com>

On 5/25/20 1:29 AM, Wang Wenhu wrote:
> Print certain name string instead of hard-coded "memory" for dev_err
> output, which would be more accurate and helpful for debugging.
> 
> Signed-off-by: Wang Wenhu <wenhu.wang@vivo.com>
> Cc: Alex Elder <elder@kernel.org>

Good idea.

Reviewed-by: Alex Elder <elder@linaro.org>

> ---
>   drivers/net/ipa/ipa_clock.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/ipa/ipa_clock.c b/drivers/net/ipa/ipa_clock.c
> index ddbd687fe64b..749ff5668e37 100644
> --- a/drivers/net/ipa/ipa_clock.c
> +++ b/drivers/net/ipa/ipa_clock.c
> @@ -66,8 +66,8 @@ ipa_interconnect_init_one(struct device *dev, const char *name)
>   
>   	path = of_icc_get(dev, name);
>   	if (IS_ERR(path))
> -		dev_err(dev, "error %ld getting memory interconnect\n",
> -			PTR_ERR(path));
> +		dev_err(dev, "error %ld getting %s interconnect\n",
> +			PTR_ERR(path), name);
>   
>   	return path;
>   }
> 


  reply	other threads:[~2020-05-26  0:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  6:29 Wang Wenhu
2020-05-26  0:49 ` Alex Elder [this message]
2020-05-26  1:04 ` David Miller

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=75dd9de2-c8a8-945a-fb14-26c3c6044bb6@ieee.org \
    --to=elder@ieee.org \
    --cc=davem@davemloft.net \
    --cc=elder@kernel.org \
    --cc=kernel@vivo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wenhu.wang@vivo.com \
    /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

all inboxes | Powered by JetHome®