mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: wangyufen <wangyufen@huawei.com>
To: Vincent MAILHOL <mailhol.vincent@wanadoo.fr>
Cc: <gregkh@linuxfoundation.org>, <linus.walleij@linaro.org>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] USB: FHCI: fix error return code in of_fhci_probe()
Date: Tue, 29 Nov 2022 14:17:54 +0800	[thread overview]
Message-ID: <da3dec73-e089-44ef-9167-b5fd990cc4fc@huawei.com> (raw)
In-Reply-To: <CAMZ6Rq+Y=7Cr8n68UMQ9FyfcZdNnHwaW5dabVf4CnaMadW90DQ@mail.gmail.com>



在 2022/11/29 12:11, Vincent MAILHOL 写道:
> On Tue. 29 nov. 2022 à 12:33, Wang Yufen <wangyufen@huawei.com> wrote:
>> Fix to return a negative error code of PTR_ERR(fhci->gpiods[i])
>> instead of 0.
>>
>> Fixes: a4efdb8a423b ("USB: FHCI: Switch to GPIO descriptors")
>> Signed-off-by: Wang Yufen <wangyufen@huawei.com>
>> ---
>>   drivers/usb/host/fhci-hcd.c | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/usb/host/fhci-hcd.c b/drivers/usb/host/fhci-hcd.c
>> index 95a4446..afef72a 100644
>> --- a/drivers/usb/host/fhci-hcd.c
>> +++ b/drivers/usb/host/fhci-hcd.c
>> @@ -639,6 +639,7 @@ static int of_fhci_probe(struct platform_device *ofdev)
>>                                          NULL, i, GPIOD_OUT_LOW);
>>
>>                  if (IS_ERR(fhci->gpiods[i])) {
>> +                       ret = PTR_ERR(fhci->gpiods[i])
>>                          dev_err(dev, "incorrect GPIO%d: %ld\n",
>>                                  i, PTR_ERR(fhci->gpiods[i]));
> 
> Can you add some extra clean-up and reuse ret in the dev_err()?
> 
>                           dev_err(dev, "incorrect GPIO%d: %ld\n", i, ret);

I prefer to reuse ret, just like other fhci->*** checks. This also keeps 
the code style consistent with the context. Will change in v2.
Thanks.

> 
> Alternatively you can also consider %pe to print the mnemotechnic
> instead of the value:
> 
>                           dev_err(dev, "incorrect GPIO%d: %pe\n",
>                                   i, fhci->gpiods[i]);
> 
> 
> Yours sincerely,
> Vincent Mailhol
> 

      reply	other threads:[~2022-11-29  6:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29  3:33 Wang Yufen
2022-11-29  4:11 ` Vincent MAILHOL
2022-11-29  6:17   ` wangyufen [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=da3dec73-e089-44ef-9167-b5fd990cc4fc@huawei.com \
    --to=wangyufen@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mailhol.vincent@wanadoo.fr \
    /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®