From: zhong jiang <zhongjiang@huawei.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: <alcooperx@gmail.com>, <kishon@ti.com>, <robh@kernel.org>,
<hauke@hauke-m.de>, <ralf@linux-mips.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] phy:phy-brcm-us: Use PTR_ERR_OR_ZERO to replace the open code
Date: Thu, 16 Aug 2018 09:30:19 +0800 [thread overview]
Message-ID: <5B74D3AB.8010605@huawei.com> (raw)
In-Reply-To: <7ba3b0be-4538-87a1-15f4-f2cbc6e12e66@gmail.com>
On 2018/8/16 7:23, Florian Fainelli wrote:
> On 08/13/2018 04:24 AM, zhong jiang wrote:
>> PTR_ERR_OR_ZERO has implemented the if(IS_ERR(...)) + PTR_ERR, So
>> just replace them rather than duplicating its implement.
> Subject should be:
>
> phy: phy-brcm-usb: Use PTR_ERR_OR_ZERO to replace open coded version
Thank you for tips. It is my mistake.:-[
Sincerely,
zhong jiang
> Thank you
>
>> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
>> ---
>> drivers/phy/broadcom/phy-brcm-usb.c | 4 +---
>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/drivers/phy/broadcom/phy-brcm-usb.c b/drivers/phy/broadcom/phy-brcm-usb.c
>> index d1dab36..f59b1dc 100644
>> --- a/drivers/phy/broadcom/phy-brcm-usb.c
>> +++ b/drivers/phy/broadcom/phy-brcm-usb.c
>> @@ -372,10 +372,8 @@ static int brcm_usb_phy_probe(struct platform_device *pdev)
>> clk_disable(priv->usb_30_clk);
>>
>> phy_provider = devm_of_phy_provider_register(dev, brcm_usb_phy_xlate);
>> - if (IS_ERR(phy_provider))
>> - return PTR_ERR(phy_provider);
>>
>> - return 0;
>> + return PTR_ERR_OR_ZERO(phy_provider);
>> }
>>
>> #ifdef CONFIG_PM_SLEEP
>>
>
next prev parent reply other threads:[~2018-08-16 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 11:24 [PATCH 0/2] phy: Use PTR_ERR_OR_ZERO to replace the open code zhong jiang
2018-08-13 11:24 ` [PATCH 1/2] phy:phy-brcm-us: " zhong jiang
2018-08-15 23:23 ` Florian Fainelli
2018-08-16 1:30 ` zhong jiang [this message]
2018-08-13 11:24 ` [PATCH 2/2] phy:phy-lantiq-rcu-usb2: " zhong jiang
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=5B74D3AB.8010605@huawei.com \
--to=zhongjiang@huawei.com \
--cc=alcooperx@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.