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 3/6] iio: adc: ad7124: use guard(mutex) to simplify return paths
Date: Wed, 10 Sep 2025 17:27:50 +0100 [thread overview]
Message-ID: <20250910172750.156bb1ae@jic23-huawei> (raw)
In-Reply-To: <20250907110652.295b296b@jic23-huawei>
On Sun, 7 Sep 2025 11:06:52 +0100
Jonathan Cameron <jic23@kernel.org> wrote:
> On Fri, 05 Sep 2025 13:11:58 -0500
> David Lechner <dlechner@baylibre.com> wrote:
>
> > Use guard(mutex) in a couple of functions to allow direct returns. This
> > simplifies the code a bit and will make later changes easier.
> >
> > Signed-off-by: David Lechner <dlechner@baylibre.com>
> Another nice improvement that stands on it's own.
>
> Applied.
>
Unapplied due to drop of the precursor fix. Same with patches 1 and 2.
J
next prev parent reply other threads:[~2025-09-10 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 18:11 [PATCH 0/6] iio: adc: ad7124: add filter support David Lechner
2025-09-05 18:11 ` [PATCH 1/6] iio: adc: ad7124: use clamp() David Lechner
2025-09-07 10:02 ` Jonathan Cameron
2025-09-05 18:11 ` [PATCH 2/6] iio: adc: ad7124: use read_avail() for scale_available David Lechner
2025-09-07 10:04 ` Jonathan Cameron
2025-09-05 18:11 ` [PATCH 3/6] iio: adc: ad7124: use guard(mutex) to simplify return paths David Lechner
2025-09-07 10:06 ` Jonathan Cameron
2025-09-10 16:27 ` Jonathan Cameron [this message]
2025-09-05 18:11 ` [PATCH 4/6] iio: adc: ad7124: support fractional sampling_frequency David Lechner
2025-09-05 18:12 ` [PATCH 5/6] iio: adc: ad7124: add filter support David Lechner
2025-09-07 10:22 ` Jonathan Cameron
2025-09-10 16:29 ` Jonathan Cameron
2025-09-05 18:12 ` [PATCH 6/6] iio: ABI: document "sinc4+rej60" filter_type David Lechner
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=20250910172750.156bb1ae@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