RE: [PATCH v3 0/6] iio: use dev_err_probe in probe path for ADI drivers

[Miclaus, Antoniu]

--
Antoniu Miclăuş

> -----Original Message-----
> From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxx>
> Sent: Wednesday, February 25, 2026 6:15 PM
> To: Miclaus, Antoniu <Antoniu.Miclaus@xxxxxxxxxx>
> Cc: Lars-Peter Clausen <lars@xxxxxxxxxx>; Hennerich, Michael
> <Michael.Hennerich@xxxxxxxxxx>; Jonathan Cameron <jic23@xxxxxxxxxx>;
> David Lechner <dlechner@xxxxxxxxxxxx>; Sa, Nuno <Nuno.Sa@xxxxxxxxxx>;
> Andy Shevchenko <andy@xxxxxxxxxx>; linux-iio@xxxxxxxxxxxxxxx; linux-
> kernel@xxxxxxxxxxxxxxx
> Subject: Re: [PATCH v3 0/6] iio: use dev_err_probe in probe path for ADI
> drivers
> 
> [External]
> 
> On Wed, Feb 25, 2026 at 05:05:46PM +0200, Antoniu Miclaus wrote:
> > Use dev_err_probe() consistently in the probe path of several ADI IIO
> > drivers. This simplifies error handling and ensures proper logging of
> > deferred probes.
> >
> > Each driver is updated by introducing a local struct device variable to
> > simplify repeated &spi->dev / &client->dev references, and converting
> > error paths to use dev_err_probe().
> >
> > Drivers updated:
> >  - adrf6780
> >  - admv1014
> >  - admv1013
> >  - adf4377
> >  - ad7293
> >  - admv8818
> >
> > Changes in v3:
> >  - Squash the struct device variable introduction and dev_err_probe()
> >    conversion into a single patch per driver.
> 
> Why? Maybe my comment was unclear previous time.
> 
> The idea is to convert to short dev the only lines that are not being touched
> by the second (dev_err_probe() conversion) patch.

Sure, so for the function which use dev only for the dev errors I introduce the struct device *dev = &spi->dev; in the dev_error_probe patch?

> 
> --
> With Best Regards,
> Andy Shevchenko
>