mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: lucas.p.stankus@gmail.com, lars@metafoo.de,
	Michael.Hennerich@analog.com, puranjay@kernel.org,
	cosmin.tanislav@analog.com, marcelo.schmitt@analog.com,
	antoniu.miclaus@analog.com, ramona.gradinariu@analog.com,
	dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] iio: accel: small cleanups and error-handling improvements
Date: Sun, 19 Apr 2026 22:49:53 +0530	[thread overview]
Message-ID: <C4D894F3-CB25-4641-AD48-291E3FDE35DD@gmail.com> (raw)
In-Reply-To: <20260419173408.0d17995a@jic23-huawei>



On 19 April 2026 10:04:08 pm IST, Jonathan Cameron <jic23@kernel.org> wrote:
>On Fri, 17 Apr 2026 18:19:16 +0530
>Sanjay Chitroda <sanjayembeddedse@gmail.com> wrote:
>
>> From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
>> 
>> Hi all,
>> 
>> This series contains a few small cleanups and robustness improvements to
>> adxl313, adxl380, adxl355, adxl367 and adxl372 IIO accelerometer drivers.
>
>0/2  in patch title? It's fine for that bit to change from version to version.
>
>Anyhow, I tweaked as Andy suggested whilst applying and picked up the lot.
>
>Note however, that the advantage of devm_mutex_init() is minor at best,
>which is why we didn't bother with mutex_destroy() most of the time
>before this convenient way of calling it existed.  Combined with
>dev_err_probe() being nice but minor cleanup, I'd generally reserved these
>sorts of changes for when someone is otherwise working on a driver or
>doing a more thorough modernisation.
>
>I don't mind people doing this sort of thing for one of their first
>few patches, so what you have here is fine, but it's not suitable material
>for a mass cleanup of the whole subsystem!
>
>Thanks,
>
>Jonathan

Hi Jonathan,

Thank you for your input, assistance and considering the changes.

I understand and agree, will take care this part.
>
>> 
>> The changes modernize mutex handling using devm-managed helpers.
>> In addition, error handling during probe is cleaned up by switching to
>> dev_err_probe() to better handle deferred probing.
>> 
>> Changes in v2:
>> - Drop guard() changes as it's already available in iio/testing.
>> - Rebase changes on top of iio/testing with guidance from Andy.
>> - Added new change for additional iio accel drivers.
>> 
>> No functional changes are intended.
>> 
>> Testing:
>>   - Compiled with W=1
>>   - Build-tested on QEMU x86_64
>> 
>> Thanks,
>> Sanjay Chitroda
>> 
>> Sanjay Chitroda (8):
>>   iio: accel: adxl313_core: Use devm-managed mutex initialization
>>   iio: accel: adxl313: Use dev_err_probe
>>   iio: accel: adxl380: Use devm-managed mutex initialization
>>   iio: accel: adxl355_core: Use devm-managed mutex initialization
>>   iio: accel: adxl355: Use dev_err_probe
>>   iio: accel: adxl367: Use devm-managed mutex initialization
>>   iio: accel: adxl372: Use devm-managed mutex initialization
>>   iio: accel: adxl372: Use dev_err_probe
>> 
>>  drivers/iio/accel/adxl313_core.c | 10 +++++-----
>>  drivers/iio/accel/adxl313_i2c.c  | 10 ++++------
>>  drivers/iio/accel/adxl313_spi.c  | 10 ++++------
>>  drivers/iio/accel/adxl355_core.c | 28 +++++++++++-----------------
>>  drivers/iio/accel/adxl355_i2c.c  | 11 ++++-------
>>  drivers/iio/accel/adxl355_spi.c  | 11 ++++-------
>>  drivers/iio/accel/adxl367.c      |  4 +++-
>>  drivers/iio/accel/adxl372.c      | 10 +++++-----
>>  drivers/iio/accel/adxl380.c      |  4 +++-
>>  9 files changed, 43 insertions(+), 55 deletions(-)
>> 
>> 
>> base-commit: 0ccdcdc698b7ba52f2c9bc09bfdf9f020ca0e6e6
>

      reply	other threads:[~2026-04-19 17:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17 12:49 Sanjay Chitroda
2026-04-17 12:49 ` [PATCH v2 1/8] iio: accel: adxl313_core: Use devm-managed mutex initialization Sanjay Chitroda
2026-04-17 12:49 ` [PATCH v2 2/8] iio: accel: adxl313: Use dev_err_probe Sanjay Chitroda
2026-04-17 18:35   ` Andy Shevchenko
2026-04-17 18:47     ` Sanjay Chitroda
2026-04-18  0:15       ` Andy Shevchenko
2026-04-17 12:49 ` [PATCH v2 3/8] iio: accel: adxl380: Use devm-managed mutex initialization Sanjay Chitroda
2026-04-17 12:49 ` [PATCH v2 4/8] iio: accel: adxl355_core: " Sanjay Chitroda
2026-04-17 12:49 ` [PATCH v2 5/8] iio: accel: adxl355: Use dev_err_probe Sanjay Chitroda
2026-04-17 12:49 ` [PATCH v2 6/8] iio: accel: adxl367: Use devm-managed mutex initialization Sanjay Chitroda
2026-04-17 12:49 ` [PATCH v2 7/8] iio: accel: adxl372: " Sanjay Chitroda
2026-04-17 12:49 ` [PATCH v2 8/8] iio: accel: adxl372: Use dev_err_probe Sanjay Chitroda
2026-04-17 19:20   ` Sanjay Chitroda
2026-04-18  7:01     ` Cosmin Tanislav
2026-04-19 16:34 ` [PATCH 0/2] iio: accel: small cleanups and error-handling improvements Jonathan Cameron
2026-04-19 17:19   ` Sanjay Chitroda [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=C4D894F3-CB25-4641-AD48-291E3FDE35DD@gmail.com \
    --to=sanjayembeddedse@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=antoniu.miclaus@analog.com \
    --cc=cosmin.tanislav@analog.com \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.p.stankus@gmail.com \
    --cc=marcelo.schmitt@analog.com \
    --cc=nuno.sa@analog.com \
    --cc=puranjay@kernel.org \
    --cc=ramona.gradinariu@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

Powered by JetHome