[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aYITRNfRgK475ck-@smile.fi.intel.com>
Date: Tue, 3 Feb 2026 17:24:52 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
Cc: Jonathan Cameron <jic23@...nel.org>,
David Lechner <dlechner@...libre.com>,
Nuno Sá <nuno.sa@...log.com>,
Andy Shevchenko <andy@...nel.org>,
Antoniu Miclaus <antoniu.miclaus@...log.com>,
Andrew Ijano <andrew.ijano@...il.com>, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
error27@...il.com, David Lechner <dlechner@...libe.com>
Subject: Re: [PATCH v3 next 4/6] iio: sca3000: stop interrupts via
devm_add_action_or_reset()
On Tue, Feb 03, 2026 at 04:20:48AM -0800, Harshit Mogalapalli wrote:
> sca3000_stop_all_interrupts() is moved above the probe routine so the
> new function sca3000_disable_interrupts() used in probe can directly
> call it without additional declaration.
>
> Used devm_add_action_or_reset() for shutting down the interrupts.
> Make sca3000_stop_all_interrupts() return void now that it always hooks
> into devm cleanup.
>
> No functional change intended.
...
> + mutex_lock(&st->lock);
> +out_unlock:
> + mutex_unlock(&st->lock);
You copy the code that is going to be removed. It means the conversion to
guard()() should be done before this patch.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists