On Wed, Dec 13, 2023 at 08:48:55PM +0200, Andy Shevchenko wrote:
> On Wed, Dec 13, 2023 at 07:33:49PM +0100, Uwe Kleine-König wrote:
> > On Wed, Dec 13, 2023 at 08:16:26PM +0200, Andy Shevchenko wrote:
> > > On Tue, Dec 12, 2023 at 11:20:53AM +0300, Nikita Shubin wrote:
> > > > Drop legacy acquire/release since we are using pinctrl for this now.
>
> ...
>
> > > I think you wanted
> > >
> > > ret = PTR_ERR_OR_ZERO(drv_data->dma_rx_channel);
> > > if (ret)
> > > return dev_err_probe(dev, ret, "rx DMA setup failed");
> >
> > How is that different from
> >
> > if (IS_ERR(drv_data->dma_rx_channel))
> > return dev_err_probe(dev, PTR_ERR(drv_data->dma_rx_channel), "....");
> >
> > (which seems to be more idiomatic to me)? While I was involved in
> > creating PTR_ERR_OR_ZERO, I don't particularily like it (today).
>
> Makes lines shorter, either works for me.
If you want shorter lines, I'd prefer
if (IS_ERR(drv_data->dma_rx_channel)) {
ret = PTR_ERR(drv_data->dma_rx_channel);
return dev_err_probe(dev, ret, "...\n");
}
over
ret = PTR_ERR_OR_ZERO(drv_data->dma_rx_channel);
if (ret)
return dev_err_probe(dev, ret, "\n");
even though it's one line longer because the if body needs curly braces.
I think it's easier to parse for a human which IMHO matters more than
the additional line. But I'm aware that might be subjective.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
Attachment:
signature.asc
Description: PGP signature
