From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Felipe Ribeiro de Souza <felipers@ime.usp.br>,
andy@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
paul@crapouillou.net, linux-iio@vger.kernel.org,
linux-mips@vger.kernel.org
Subject: Re: [PATCH v5 0/3] iio: adc: ingenic-adc: use guard()() to handle synchronisation and refactor lock-held helpers
Date: Wed, 6 May 2026 19:12:49 +0100 [thread overview]
Message-ID: <20260506191249.18d5dd1f@jic23-huawei> (raw)
In-Reply-To: <afsH24xuP1GF9jYz@ashevche-desk.local>
On Wed, 6 May 2026 12:20:27 +0300
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> On Tue, May 05, 2026 at 11:24:27PM -0300, Felipe Ribeiro de Souza wrote:
> > In drivers/iio/adc/ingenic-adc.c:
> > - Refactor ingenic_adc_read_chan_info_raw() and ingenic_adc_enable_unlocked()
> > - Replace mutex_lock() and mutex_unlock() calls with guard()()
>
> This version LGTM,
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
>
> In case you want to cook more cleanups, I provided a couple of side notes.
>
Applied to the testing branch of iio.git
thanks
Jonathan
prev parent reply other threads:[~2026-05-06 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 2:24 [PATCH v5 0/3] iio: adc: ingenic-adc: use guard()() to handle synchronisation and refactor lock-held helpers Felipe Ribeiro de Souza
2026-05-06 2:24 ` [PATCH v5 1/3] iio: adc: ingenic-adc: rename ingenic_adc_enable_unlocked() function Felipe Ribeiro de Souza
2026-05-06 2:24 ` [PATCH v5 2/3] iio: adc: ingenic-adc: refactor ingenic_adc_read_chan_info_raw() Felipe Ribeiro de Souza
2026-05-06 2:24 ` [PATCH v5 3/3] iio: adc: ingenic-adc: use guard()() and scoped_guard() to handle synchronisation Felipe Ribeiro de Souza
2026-05-06 9:19 ` Andy Shevchenko
2026-05-06 9:20 ` [PATCH v5 0/3] iio: adc: ingenic-adc: use guard()() to handle synchronisation and refactor lock-held helpers Andy Shevchenko
2026-05-06 18:12 ` Jonathan Cameron [this message]
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=20260506191249.18d5dd1f@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=felipers@ime.usp.br \
--cc=linux-iio@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=paul@crapouillou.net \
/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