Linux USB
 help / color / mirror / Atom feed
From: Yang Yingliang <yangyingliang@huawei.com>
To: Sergei Shtylyov <sergei.shtylyov@gmail.com>, <linux-usb@vger.kernel.org>
Cc: <gregkh@linuxfoundation.org>, <b-liu@ti.com>
Subject: Re: [PATCH -next resend 1/5] usb: musb: core: Switch to use dev_err_probe() helper
Date: Tue, 27 Sep 2022 09:17:28 +0800	[thread overview]
Message-ID: <4ec33092-dac3-ff00-9001-58542122278b@huawei.com> (raw)
In-Reply-To: <6d8b99a0-f12b-caaa-5fcd-a7a4a7d6e219@gmail.com>

Hi,

On 2022/9/27 3:12, Sergei Shtylyov wrote:
> Hello!
>
> On 9/26/22 5:15 PM, Yang Yingliang wrote:
>
>> In the probe path, dev_err() can be replaced with dev_err_probe()
>> which will check if error code is -EPROBE_DEFER and prints the
>> error name. It also sets the defer probe reason which can be
>> checked later through debugfs. It's more simple in error path.
>>
>> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
>> ---
>>   drivers/usb/musb/musb_core.c | 5 ++---
>>   1 file changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
>> index bbbcfd49fb35..37ef9d8cb8ea 100644
>> --- a/drivers/usb/musb/musb_core.c
>> +++ b/drivers/usb/musb/musb_core.c
>> @@ -2595,9 +2595,8 @@ musb_init_controller(struct device *dev, int nIrq, void __iomem *ctrl)
>>   	musb_platform_exit(musb);
>>   
>>   fail1:
>> -	if (status != -EPROBE_DEFER)
>> -		dev_err(musb->controller,
>> -			"%s failed with status %d\n", __func__, status);
>> +	dev_err_probe(musb->controller, status,
>> +		      "%s failed with status\n", __func__);
>     Printing "with status" when you no longer print the status itself has no sense.
Yes, " with status" string should be removed.

Thanks,
Yang
>
> [...]
>
> MBR, Sergey
> .

  reply	other threads:[~2022-09-27  1:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26 14:15 [PATCH -next resend 0/5] usb: musb: Switch to use dev_err_probe() helper Yang Yingliang
2022-09-26 14:15 ` [PATCH -next resend 1/5] usb: musb: core: " Yang Yingliang
2022-09-26 19:12   ` Sergei Shtylyov
2022-09-27  1:17     ` Yang Yingliang [this message]
2022-09-26 14:15 ` [PATCH -next resend 2/5] usb: musb: da8xx: " Yang Yingliang
2022-09-26 14:15 ` [PATCH -next resend 3/5] usb: musb: cppi41: " Yang Yingliang
2022-09-26 14:15 ` [PATCH -next resend 4/5] usb: musb: jz4740: " Yang Yingliang
2022-09-26 14:15 ` [PATCH -next resend 5/5] usb: musb: sunxi: " Yang Yingliang

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=4ec33092-dac3-ff00-9001-58542122278b@huawei.com \
    --to=yangyingliang@huawei.com \
    --cc=b-liu@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sergei.shtylyov@gmail.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