From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Crofts via B4 Relay <devnull+joshua.crofts1.gmail.com@kernel.org>
Cc: joshua.crofts1@gmail.com, "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Alexander Koch" <mail@alexanderkoch.net>,
"Michael Hornung" <mhornung.linux@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andy Shevchenko" <andriy.shevchenko@intel.com>
Subject: Re: [PATCH v2 08/10] iio: light: opt3001: move driver to guard(mutex)() use
Date: Sat, 16 May 2026 13:05:37 +0100 [thread overview]
Message-ID: <20260516130537.78255297@jic23-huawei> (raw)
In-Reply-To: <20260512-opt3001-cleanup-v2-8-8018cf3a8a0a@gmail.com>
On Tue, 12 May 2026 12:57:28 +0200
Joshua Crofts via B4 Relay <devnull+joshua.crofts1.gmail.com@kernel.org> wrote:
> From: Joshua Crofts <joshua.crofts1@gmail.com>
>
> Move driver to use guard(mutex)() macro, to facilitate automatic
> locking/unlocking of resources. This modernizes the driver and
> improves code style.
>
> While at it, remove unnecessary gotos and return variables.
>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> Signed-off-by: Joshua Crofts <joshua.crofts1@gmail.com>
A couple of very trivial things where I'd have done it differently.
I don't mind much however if you want to keep it as is.
> @@ -615,18 +601,12 @@ static int opt3001_write_event_value(struct iio_dev *iio,
> opt->low_thresh_exp = exponent;
> break;
> default:
> - ret = -EINVAL;
> - goto err;
> + return -EINVAL;
> }
>
> ret = i2c_smbus_write_word_swapped(client, reg, value);
> - if (ret < 0) {
> + if (ret < 0)
> dev_err(dev, "failed to write register %02x\n", reg);
> - goto err;
Similar to below. Though very much a matter of personal taste - I'd
definitely not have asked for a respin for this alone!
> - }
> -
> -err:
> - mutex_unlock(&opt->lock);
>
> return ret;
> }
> @@ -660,7 +640,7 @@ static int opt3001_write_event_config(struct iio_dev *iio,
> if (!state && opt->mode == OPT3001_CONFIGURATION_M_SHUTDOWN)
> return 0;
>
> - mutex_lock(&opt->lock);
> + guard(mutex)(&opt->lock);
>
> mode = state ? OPT3001_CONFIGURATION_M_CONTINUOUS
> : OPT3001_CONFIGURATION_M_SHUTDOWN;
> @@ -669,21 +649,16 @@ static int opt3001_write_event_config(struct iio_dev *iio,
> if (ret < 0) {
> dev_err(dev, "failed to read register %02x\n",
> OPT3001_CONFIGURATION);
> - goto err;
> + return ret;
> }
>
> reg = ret;
> opt3001_set_mode(opt, ®, mode);
>
> ret = i2c_smbus_write_word_swapped(client, OPT3001_CONFIGURATION, reg);
> - if (ret < 0) {
> + if (ret < 0)
> dev_err(dev, "failed to write register %02x\n",
> OPT3001_CONFIGURATION);
> - goto err;
I'd return ret here
> - }
> -
Then return 0; here
Makes it a little easier to spot the good path.
> -err:
> - mutex_unlock(&opt->lock);
>
> return ret;
> }
>
next prev parent reply other threads:[~2026-05-16 12:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 10:57 [PATCH v2 00/10] iio: light: opt3001: driver cleanup Joshua Crofts via B4 Relay
2026-05-12 10:57 ` [PATCH v2 01/10] iio: light: opt3001: move device registration to end of probe() Joshua Crofts via B4 Relay
2026-05-16 11:56 ` Jonathan Cameron
2026-05-12 10:57 ` [PATCH v2 02/10] iio: light: opt3001: make headers conform to iwyu Joshua Crofts via B4 Relay
2026-05-16 11:58 ` Jonathan Cameron
2026-05-12 10:57 ` [PATCH v2 03/10] iio: light: opt3001: use macros from bits.h header Joshua Crofts via B4 Relay
2026-05-16 12:00 ` Jonathan Cameron
2026-05-12 10:57 ` [PATCH v2 04/10] iio: light: opt3001: use local struct device and i2c_client variables Joshua Crofts via B4 Relay
2026-05-12 11:09 ` Andy Shevchenko
2026-05-12 11:13 ` Joshua Crofts
2026-05-12 11:27 ` Andy Shevchenko
2026-05-16 12:02 ` Jonathan Cameron
2026-05-12 10:57 ` [PATCH v2 05/10] iio: light: opt3001: ensure correct parenthesis alignment Joshua Crofts via B4 Relay
2026-05-12 10:57 ` [PATCH v2 06/10] iio: light: opt3001: localize for loop iterator Joshua Crofts via B4 Relay
2026-05-12 15:40 ` Andy Shevchenko
2026-05-12 10:57 ` [PATCH v2 07/10] iio: light: opt3001: prefer dev_err_probe() Joshua Crofts via B4 Relay
2026-05-12 15:43 ` Andy Shevchenko
2026-05-12 10:57 ` [PATCH v2 08/10] iio: light: opt3001: move driver to guard(mutex)() use Joshua Crofts via B4 Relay
2026-05-16 12:05 ` Jonathan Cameron [this message]
2026-05-12 10:57 ` [PATCH v2 09/10] iio: light: opt3001: switch driver to managed resources Joshua Crofts via B4 Relay
2026-05-12 14:26 ` Jonathan Cameron
2026-05-12 14:32 ` Joshua Crofts
2026-05-16 12:10 ` Jonathan Cameron
2026-05-12 10:57 ` [PATCH v2 10/10] iio: light: opt3001: add comment to mutex Joshua Crofts via B4 Relay
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=20260516130537.78255297@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=devnull+joshua.crofts1.gmail.com@kernel.org \
--cc=dlechner@baylibre.com \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@alexanderkoch.net \
--cc=mhornung.linux@gmail.com \
--cc=nuno.sa@analog.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