From: Jonathan Cameron <jic23@kernel.org>
To: Rajveer Chaudhari <rajveer.chaudhari.linux@gmail.com>
Cc: lucas.p.stankus@gmail.com, lars@metafoo.de,
Michael.Hennerich@analog.com, nuno.sa@analog.com,
andy@kernel.org, puranjay@kernel.org, dlechner@baylibre.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] iio: accel: convert to guard(mutex)
Date: Sat, 7 Mar 2026 10:26:34 +0000 [thread overview]
Message-ID: <20260307102634.6eaafab5@jic23-huawei> (raw)
In-Reply-To: <20260307101758.50091-1-rajveer.chaudhari.linux@gmail.com>
On Sat, 7 Mar 2026 15:47:55 +0530
Rajveer Chaudhari <rajveer.chaudhari.linux@gmail.com> wrote:
> This series converts manual mutex_lock/mutex_unlock pairs to
> guard(mutex) in three ADXL accelerometer drivers. Each conversion
> also simplifies error handling by removing goto labels and
> returning directly where possible.
>
> v3: Remove remaining goto labels completely as requested by David Lechner.
> Return directly from functions where ret variable is not needed.
> v2: Split into one patch per driver as requested by David Lechner.
> Ensured each conversion also simplifies code flow.
>
> Rajveer Chaudhari (3):
> iio: accel: adxl313: convert to guard(mutex)
> iio: accel: adxl355: convert to guard(mutex)
> iio: accel: adxl372: convert to guard(mutex)
>
> drivers/iio/accel/adxl313_core.c | 15 ++----
> drivers/iio/accel/adxl355_core.c | 81 ++++++++++++++------------------
> drivers/iio/accel/adxl372.c | 16 +++----
> 3 files changed, 45 insertions(+), 67 deletions(-)
>
Hi Rajveer,
Small process thing. Please send each new version as a separate email
thread. It can get very hard to follow when we end up with deeply
nested threads so most areas of the kernel prefer to just associate
them via name of the thread and possibly a link in the cover letter
to the previous version.
Jonathan
next prev parent reply other threads:[~2026-03-07 10:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 20:26 [PATCH] iio: " Rajveer Chaudhari
2026-03-06 20:37 ` David Lechner
2026-03-06 21:11 ` [PATCH v2 0/3] iio: accel: " Rajveer Chaudhari
2026-03-06 21:11 ` [PATCH v2 1/3] iio: accel: adxl313: " Rajveer Chaudhari
2026-03-06 22:10 ` David Lechner
2026-03-06 21:11 ` [PATCH v2 2/3] iio: accel: adxl355: " Rajveer Chaudhari
2026-03-06 22:12 ` David Lechner
2026-03-06 21:11 ` [PATCH v2 3/3] iio: accel: adxl372: " Rajveer Chaudhari
2026-03-07 10:17 ` [PATCH v3 0/3] iio: accel: " Rajveer Chaudhari
2026-03-07 10:17 ` [PATCH v3 1/3] iio: accel: adxl313: " Rajveer Chaudhari
2026-03-07 10:31 ` Jonathan Cameron
2026-03-07 10:17 ` [PATCH v3 2/3] iio: accel: adxl355: " Rajveer Chaudhari
2026-03-07 10:39 ` Jonathan Cameron
2026-03-07 10:43 ` Jonathan Cameron
2026-03-07 10:17 ` [PATCH v3 3/3] iio: accel: adxl372: " Rajveer Chaudhari
2026-03-07 10:41 ` Jonathan Cameron
2026-03-07 10:26 ` Jonathan Cameron [this message]
2026-03-07 10:33 ` [PATCH v3 0/3] iio: accel: " Rajveer Chaudhari
2026-03-07 17:08 ` Jonathan Cameron
2026-03-06 21:12 ` [PATCH] iio: " Andy Shevchenko
2026-03-06 21:23 ` Rajveer Chaudhari
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=20260307102634.6eaafab5@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.p.stankus@gmail.com \
--cc=nuno.sa@analog.com \
--cc=puranjay@kernel.org \
--cc=rajveer.chaudhari.linux@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®