From: Himanshu Jha <himanshujha199640@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: bhelgaas@google.com, jonathanh@nvidia.com,
linux-tegra@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: tegra: Use PTR_ERR_OR_ZERO
Date: Tue, 29 Aug 2017 19:44:01 +0530 [thread overview]
Message-ID: <20170829141401.GA18389@himanshu-Vostro-3559> (raw)
In-Reply-To: <20170829135517.GA30733@ulmo>
On Tue, Aug 29, 2017 at 03:55:17PM +0200, Thierry Reding wrote:
> On Tue, Aug 29, 2017 at 07:09:00PM +0530, Himanshu Jha wrote:
> > Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
> >
> > Signed-off-by: Himanshu Jha <himanshujha199640@gmail.com>
> > ---
> > drivers/pci/host/pci-tegra.c | 5 +----
> > 1 file changed, 1 insertion(+), 4 deletions(-)
> >
> > diff --git a/drivers/pci/host/pci-tegra.c b/drivers/pci/host/pci-tegra.c
> > index 9c40da5..90cda5b 100644
> > --- a/drivers/pci/host/pci-tegra.c
> > +++ b/drivers/pci/host/pci-tegra.c
> > @@ -1156,10 +1156,7 @@ static int tegra_pcie_resets_get(struct tegra_pcie *pcie)
> > return PTR_ERR(pcie->afi_rst);
> >
> > pcie->pcie_xrst = devm_reset_control_get_exclusive(dev, "pcie_x");
> > - if (IS_ERR(pcie->pcie_xrst))
> > - return PTR_ERR(pcie->pcie_xrst);
> > -
> > - return 0;
> > + return PTR_ERR_OR_ZERO(pcie->pcie_xrst);
> > }
>
> I'm not a big fan of this construct because it's a pain to undo this if
> ever we need to add code to this function. But since we do have scripts
> that will flag this, I guess this would pop up every now and again. The
> driver is unlikely to change in this part, too, so:
What do you suggest ? Shall I stop sending these patches ?
Thanks
-Himanshu Jha
> Acked-by: Thierry Reding <treding@nvidia.com>
next prev parent reply other threads:[~2017-08-29 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 13:39 Himanshu Jha
2017-08-29 13:55 ` Thierry Reding
2017-08-29 14:14 ` Himanshu Jha [this message]
2017-08-29 15:09 ` Thierry Reding
2017-08-30 13:59 ` Bjorn Helgaas
2017-08-30 14:25 ` Thierry Reding
2017-08-30 16:26 ` Bjorn Helgaas
2020-11-16 16:54 Sudip Mukherjee
2020-11-16 17:01 ` Thierry Reding
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=20170829141401.GA18389@himanshu-Vostro-3559 \
--to=himanshujha199640@gmail.com \
--cc=bhelgaas@google.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@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
all inboxes | Powered by JetHome®