public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cosmin Tanislav <demonsingur@gmail.com>
To: Sanjay Chitroda <sanjayembeddedse@gmail.com>, jic23@kernel.org
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Nuno Sá" <nuno.sa@analog.com>
Subject: Re: [PATCH v2 8/8] iio: accel: adxl372: Use dev_err_probe
Date: Sat, 18 Apr 2026 10:01:27 +0300	[thread overview]
Message-ID: <d6d8660e-c5d2-4f02-a5fc-2f8b49d2e0d7@gmail.com> (raw)
In-Reply-To: <11AEFA5E-58EF-47BA-A533-E996D395CB15@gmail.com>



On 4/17/26 10:20 PM, Sanjay Chitroda wrote:
> 
> 
> On 17 April 2026 6:19:24 pm IST, Sanjay Chitroda <sanjayembeddedse@gmail.com> wrote:
>> From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
>>
>> dev_err_probe() makes error code handling simpler and handles
>> deferred probe nicely (avoid spamming logs).
>>
>> Signed-off-by: Sanjay Chitroda <sanjayembeddedse@gmail.com>
>> ---
>> drivers/iio/accel/adxl372.c | 6 ++----
>> 1 file changed, 2 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/iio/accel/adxl372.c b/drivers/iio/accel/adxl372.c
>> index 1a6ba94f54f4..e375d068a3f5 100644
>> --- a/drivers/iio/accel/adxl372.c
>> +++ b/drivers/iio/accel/adxl372.c
>> @@ -1316,10 +1316,8 @@ int adxl372_probe(struct device *dev, struct regmap *regmap,
>> 	}
>>
>> 	ret = adxl372_setup(st);
>> -	if (ret < 0) {
>> -		dev_err(dev, "ADXL372 setup failed\n");
>> -		return ret;
>> -	}
>> +	if (ret < 0)
>> +		return dev_err_probe(dev, ret, "ADXL372 setup failed\n");
>>
>> 	if (chip_info->fifo_supported) {
>> 		ret = adxl372_buffer_setup(indio_dev);
> 
> Hi Cosmin,
> 
> Your email address listed in MAINTAINERS (cosmin.tanislav@analog.com) appears to be bouncing.
> 
> I noticed recent commits from you using cosmin-gabriel.tanislav.xa@renesas.com and demonsingur@gmail.com, so I plan to update the entry accordingly.
> 
> Could you please confirm whether you are still maintaining this subsystem with renesas/gmail account ?
> 

Hi.

Someone at Analog should be taking over as maintainer, I don't work for
Analog anymore.

CC: Nuno

> Thanks, 
> Sanjay Chitroda


      reply	other threads:[~2026-04-18  7:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17 12:49 [PATCH 0/2] iio: accel: small cleanups and error-handling improvements 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 [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=d6d8660e-c5d2-4f02-a5fc-2f8b49d2e0d7@gmail.com \
    --to=demonsingur@gmail.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=sanjayembeddedse@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