From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Maxwell Doose" <m32285159@gmail.com>,
"Tomasz Duszynski" <tduszyns@gmail.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] iio: chemical: sps30: Replace manual locking with RAII locking
Date: Tue, 2 Jun 2026 12:50:40 +0100 [thread overview]
Message-ID: <20260602125040.4a217130@jic23-huawei> (raw)
In-Reply-To: <ah6C2vFPiflM7Qvg@ashevche-desk.local>
On Tue, 2 Jun 2026 10:14:34 +0300
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> On Sat, May 23, 2026 at 01:15:36PM -0500, Maxwell Doose wrote:
> > Replace manual mutex_lock() and mutex_unlock() calls with the much newer
> > guard(mutex)() and scoped_guard() macros to enable RAII patterns,
> > modernize the driver, and to increase readability.
> >
> > Move mutex locking into sps30_do_meas() and tune it up to use guard()(),
> > as every caller takes the lock anyways.
>
> ...
>
> > - mutex_lock(&state->lock);
> > + guard(mutex)(&state->lock);
> > +
> > ret = state->ops->write_cleaning_period(state, cpu_to_be32(val));
> > - if (ret) {
> > - mutex_unlock(&state->lock);
> > + if (ret)
> > return ret;
> > - }
> >
> > msleep(20);
>
> Same question as per v4 (yes, I see that it was in the original code).
>
I relied to v4. I think it is the correct thing to do as adds a penalty
for stupid userspace code and doesn't complicate the driver like other
solutions would do.
J
prev parent reply other threads:[~2026-06-02 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 18:15 Maxwell Doose
2026-05-26 14:49 ` Jonathan Cameron
2026-06-02 7:14 ` Andy Shevchenko
2026-06-02 11:50 ` 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=20260602125040.4a217130@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.com \
--cc=nuno.sa@analog.com \
--cc=tduszyns@gmail.com \
/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
all inboxes | Powered by JetHome®