public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Salah Triki <salah.triki@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.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: dac: max5821: fix return value check in powerdown sync
Date: Mon, 27 Apr 2026 22:56:08 +0300	[thread overview]
Message-ID: <ae-_WDe36BNbdJvV@ashevche-desk.local> (raw)
In-Reply-To: <20260427184747.12149-1-salah.triki@gmail.com>

On Mon, Apr 27, 2026 at 07:47:46PM +0100, Salah Triki wrote:
> The function max5821_sync_powerdown_mode() previously returned the
> result of i2c_master_send() directly. This is problematic because:
> 
> 1. A successful I2C transfer returns the number of bytes sent (2),
>    but the caller might expect 0 for success.
> 2. If a partial transfer occurs (e.g., only 1 byte sent), it would
>    be treated as success by the caller checking for negative values.
> 
> This patch refactors the return value handling to:
> - Propagate negative error codes from the I2C core.
> - Return -EIO in case of incomplete transfers (short writes).
> - Return 0 on complete success.

So the Fixes tag is only for the case #2 from the above as the first one
is already being properly handled in the caller.

...

> -	return i2c_master_send(data->client, outbuf, 2);
> +	ret = i2c_master_send(data->client, outbuf, 2);

sizeof(outbuf)


> +

Redundant blank line.

> +	if (ret < 0)
> +		return ret;
> +
> +	if (ret != 2)

sizeof(outbuf)

> +		return -EIO;
> +
> +	return 0;

-- 
With Best Regards,
Andy Shevchenko



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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 18:47 [PATCH] iio: dac: max5821: fix return value check in powerdown sync Salah Triki
2026-04-27 19:56 ` Andy Shevchenko [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=ae-_WDe36BNbdJvV@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=salah.triki@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