From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Ethan Tidmore <ethantidmore06@gmail.com>
Cc: jic23@kernel.org, andy@kernel.org, dlechner@baylibre.com,
nuno.sa@analog.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/9] iio: light: gp2ap020a00f: simplify locking with guard()
Date: Wed, 18 Feb 2026 09:08:03 +0200 [thread overview]
Message-ID: <aZVlU9SL9e1x8Vwu@smile.fi.intel.com> (raw)
In-Reply-To: <20260218043728.609659-2-ethantidmore06@gmail.com>
On Tue, Feb 17, 2026 at 10:37:20PM -0600, Ethan Tidmore wrote:
> Use the guard() cleanup handler to manage the device lock.
> This simplifies the code by removing the need for manual unlocking
> and goto error handling paths.
> static int gp2ap020a00f_write_event_config(struct iio_dev *indio_dev,
> enum gp2ap020a00f_cmd cmd;
> int err;
>
> - mutex_lock(&data->lock);
> + guard(mutex)(&data->lock);
>
> switch (chan->type) {
> case IIO_PROXIMITY:
> err = -EINVAL;
> }
>
> - mutex_unlock(&data->lock);
> -
> return err;
> }
What I meant in the my cover letter is that you need to take some pieces from
my patches and incorporate them here, so this becomes
return 0;
...
> static int gp2ap020a00f_read_event_config(struct iio_dev *indio_dev,
> struct gp2ap020a00f_data *data = iio_priv(indio_dev);
> int event_en = 0;
>
> - mutex_lock(&data->lock);
> + guard(mutex)(&data->lock);
>
> switch (chan->type) {
> case IIO_PROXIMITY:
> @@ -1223,8 +1204,6 @@ static int gp2ap020a00f_read_event_config(struct iio_dev *indio_dev,
> break;
> }
>
> - mutex_unlock(&data->lock);
> -
> return event_en;
Same here, now event_en is redundant.
> }
...
> static int gp2ap020a00f_buffer_postenable(struct iio_dev *indio_dev)
> struct gp2ap020a00f_data *data = iio_priv(indio_dev);
> int i, err = 0;
(Do you need this '= 0'? Check it).
>
> - mutex_lock(&data->lock);
> + guard(mutex)(&data->lock);
> }
>
> if (err < 0)
> - goto error_unlock;
> + return err;
>
> data->buffer = kmalloc(indio_dev->scan_bytes, GFP_KERNEL);
> if (!data->buffer)
> err = -ENOMEM;
>
> -error_unlock:
> - mutex_unlock(&data->lock);
> -
> return err;
And here, this should become
return -ENOMEM;
return 0;
> }
...
> static int gp2ap020a00f_buffer_predisable(struct iio_dev *indio_dev)
> struct gp2ap020a00f_data *data = iio_priv(indio_dev);
> int i, err = 0;
>
> - mutex_lock(&data->lock);
> + guard(mutex)(&data->lock);
>
> iio_for_each_active_channel(indio_dev, i) {
> switch (i) {
> @@ -1452,8 +1428,6 @@ static int gp2ap020a00f_buffer_predisable(struct iio_dev *indio_dev)
> if (err == 0)
> kfree(data->buffer);
>
> - mutex_unlock(&data->lock);
> -
> return err;
> }
Same here.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-18 7:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 4:37 [PATCH v4 0/9] iio: light: gp2ap020a00f: General cleanup and Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 1/9] iio: light: gp2ap020a00f: simplify locking with guard() Ethan Tidmore
2026-02-18 7:08 ` Andy Shevchenko [this message]
2026-02-20 2:38 ` Ethan Tidmore
2026-02-20 7:43 ` Andy Shevchenko
2026-02-18 4:37 ` [PATCH v4 2/9] iio: light: gp2ap020a00f: correct return type to int Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 3/9] iio: light: gp2ap020a00f: Use correct types for 16-bit LE data Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 4/9] iio: light: gp2ap020a00f: Replace custom implementation of min() Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 5/9] iio: light: gp2ap020a00f: Return directly from the switch cases Ethan Tidmore
2026-02-19 19:32 ` Ethan Tidmore
2026-02-19 20:00 ` Andy Shevchenko
2026-02-18 4:37 ` [PATCH v4 6/9] iio: light: gp2ap020a00f: Use temporary variable for struct device Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 7/9] iio: light: gp2ap020a00f: Explicitly use string literal for driver name Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 8/9] iio: light: gp2ap020a00f: Remove trailing comma in termination entry Ethan Tidmore
2026-02-18 4:37 ` [PATCH v4 9/9] iio: light: gp2ap020a00f: Join some lines of code to be a single line Ethan Tidmore
2026-02-18 7:10 ` [PATCH v4 0/9] iio: light: gp2ap020a00f: General cleanup and Andy Shevchenko
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=aZVlU9SL9e1x8Vwu@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=ethantidmore06@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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