From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ad7124: use devm_mutex_init()
Date: Sat, 20 Sep 2025 12:06:27 +0100 [thread overview]
Message-ID: <20250920120627.307a8bdd@jic23-huawei> (raw)
In-Reply-To: <20250917-iio-adc-ad7124-use-devm_mutex_init-v1-1-ff23fe3ad954@baylibre.com>
On Wed, 17 Sep 2025 10:22:30 -0500
David Lechner <dlechner@baylibre.com> wrote:
> Use devm_mutex_init() to initialize the mutex to handle automatically
> freeing in debug builds.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
Normally I'd say this isn't worth the churn but fine this time given
all the other patches for this driver.
Applied to iio.git/testing
Jonathan
> ---
> drivers/iio/adc/ad7124.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/adc/ad7124.c b/drivers/iio/adc/ad7124.c
> index 9ace3e0914f5acab695c0382df758f56f333ae72..9d9250274b9a02e2982e6ceda27009a84413dc2f 100644
> --- a/drivers/iio/adc/ad7124.c
> +++ b/drivers/iio/adc/ad7124.c
> @@ -1482,7 +1482,10 @@ static int ad7124_setup(struct ad7124_state *st)
> st->adc_control &= ~AD7124_ADC_CONTROL_MODE;
> st->adc_control |= FIELD_PREP(AD7124_ADC_CONTROL_MODE, AD_SD_MODE_IDLE);
>
> - mutex_init(&st->cfgs_lock);
> + ret = devm_mutex_init(dev, &st->cfgs_lock);
> + if (ret)
> + return ret;
> +
> INIT_KFIFO(st->live_cfgs_fifo);
> for (i = 0; i < st->num_channels; i++) {
> struct ad7124_channel_config *cfg = &st->channels[i].cfg;
>
> ---
> base-commit: 561285d048053fec8a3d6d1e3ddc60df11c393a0
> change-id: 20250917-iio-adc-ad7124-use-devm_mutex_init-45a297b1ff8f
>
> Best regards,
prev parent reply other threads:[~2025-09-20 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 15:22 [PATCH] iio: adc: ad7124: use devm_mutex_init() David Lechner
2025-09-20 11:06 ` 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=20250920120627.307a8bdd@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--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