Re: [PATCH v5 6/8] iio: light: stk3310: use dev_err_probe where possible

2025-02-15 Thread Aren
On Sun, Feb 09, 2025 at 04:47:44PM +0200, Andy Shevchenko wrote: > On Sat, Feb 08, 2025 at 04:13:24PM -0500, Aren Moynihan wrote: > > Using dev_err_probe instead of dev_err and return makes the errors > > Use dev_err_probe() > dev_err() > > > easier to understand by including the error name, and

Re: [PATCH v5 6/8] iio: light: stk3310: use dev_err_probe where possible

2025-02-12 Thread Andy Shevchenko
On Tue, Feb 11, 2025 at 07:43:11PM +, Jonathan Cameron wrote: > On Sun, 9 Feb 2025 16:47:44 +0200 > Andy Shevchenko wrote: > > On Sat, Feb 08, 2025 at 04:13:24PM -0500, Aren Moynihan wrote: > > > Using dev_err_probe instead of dev_err and return makes the errors > > > > Use dev_err_probe()

Re: [PATCH v5 6/8] iio: light: stk3310: use dev_err_probe where possible

2025-02-11 Thread Jonathan Cameron
On Sun, 9 Feb 2025 16:47:44 +0200 Andy Shevchenko wrote: > On Sat, Feb 08, 2025 at 04:13:24PM -0500, Aren Moynihan wrote: > > Using dev_err_probe instead of dev_err and return makes the errors > > Use dev_err_probe() > dev_err() > > > easier to understand by including the error name, and save

Re: [PATCH v5 6/8] iio: light: stk3310: use dev_err_probe where possible

2025-02-09 Thread Andy Shevchenko
On Sat, Feb 08, 2025 at 04:13:24PM -0500, Aren Moynihan wrote: > Using dev_err_probe instead of dev_err and return makes the errors Use dev_err_probe() dev_err() > easier to understand by including the error name, and saves a little > code. I believe this patch will make more sense before switch