From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: zhong jiang <zhongjiang@huawei.com>
Cc: a.zummo@towertech.it, baruch@tkos.co.il,
linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] rtc:rtc-digicolor: Use PTR_ERR_OR_ZERO to replace the open code
Date: Wed, 15 Aug 2018 10:20:55 +0200 [thread overview]
Message-ID: <20180815082055.GV943@piout.net> (raw)
In-Reply-To: <5B73D368.5010205@huawei.com>
On 15/08/2018 15:16:56+0800, zhong jiang wrote:
> On 2018/8/15 0:15, Alexandre Belloni wrote:
> > Hi,
> >
> > On 13/08/2018 19:31:24+0800, zhong jiang wrote:
> >> PTR_ERR_OR_ZERO has implemented the if(IS_ERR(...)) + PTR_ERR, So
> >> just replace them rather than duplicating its implement.
> >>
> >> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
> >> ---
> >> drivers/rtc/rtc-digicolor.c | 4 +---
> >> 1 file changed, 1 insertion(+), 3 deletions(-)
> >>
> >> diff --git a/drivers/rtc/rtc-digicolor.c b/drivers/rtc/rtc-digicolor.c
> >> index b253bf1..fd6850c 100644
> >> --- a/drivers/rtc/rtc-digicolor.c
> >> +++ b/drivers/rtc/rtc-digicolor.c
> >> @@ -202,10 +202,8 @@ static int __init dc_rtc_probe(struct platform_device *pdev)
> >> platform_set_drvdata(pdev, rtc);
> >> rtc->rtc_dev = devm_rtc_device_register(&pdev->dev, pdev->name,
> >> &dc_rtc_ops, THIS_MODULE);
> >> - if (IS_ERR(rtc->rtc_dev))
> >> - return PTR_ERR(rtc->rtc_dev);
> >>
> >> - return 0;
> >> + return PTR_ERR_OR_ZERO(rtc->rtc_dev);
> > As many other maintainers, I don't find that kind of change useful and
> > I'm not taking them unless there are other improvements in the driver.
> >
> >
> Hi, Alexandre
>
> The issue is detected with the help of Coccinelle. It simplify the code with specific
> function rather than duplicating its implementation.
>
> The patch clean up the code. of course, it is not a bug. if you do not care about it.
> I am ok with that.
>
But this does not simplify or make the code clearer and as soon as you
need to add code between the devm_rtc_device_register call and the end
of the function, the patch will need to be undone.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-15 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 11:31 [PATCH 0/2] rtc: Use PTR_ERR_OR_ZERO to replace the open code zhong jiang
2018-08-13 11:31 ` [PATCH 1/2] rtc:rtc-digicolor: " zhong jiang
2018-08-14 4:18 ` Baruch Siach
2018-08-14 16:15 ` Alexandre Belloni
2018-08-15 7:16 ` zhong jiang
2018-08-15 8:20 ` Alexandre Belloni [this message]
2018-08-13 11:31 ` [PATCH 2/2] rtc:rtc-ds1347: " zhong jiang
2018-08-14 4:18 ` Baruch Siach
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=20180815082055.GV943@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=baruch@tkos.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=zhongjiang@huawei.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 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.