Linux IIO development
 help / color / mirror / Atom feed
From: Qianfeng Rong <rongqianfeng@vivo.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"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: use int instead of u32 to store error codes
Date: Mon, 1 Sep 2025 19:55:04 +0800	[thread overview]
Message-ID: <7a775ae7-5925-4d64-a030-eeaa9d5809c9@vivo.com> (raw)
In-Reply-To: <20250831162746.7dab74c2@jic23-huawei>


在 2025/8/31 23:27, Jonathan Cameron 写道:
> On Tue, 26 Aug 2025 18:18:25 +0800
> Qianfeng Rong <rongqianfeng@vivo.com> wrote:
>
>> Use int instead of unsigned int for 'ret' variable to store negative error
>> codes returned by ad5421_write_unlocked() and ad5360_write_unlocked().
>>
>> Signed-off-by: Qianfeng Rong <rongqianfeng@vivo.com>
> This is a fix, so needs a fixes tag.
>
> Given the two drivers were introduced in separate patches
> I would suggest splitting this into two different patches so
> we can call out how far to backport each one (via the appropriate
> fixes tags!)

Okay, I’ll send the V2 version later.

Best regards,
Qianfeng


      reply	other threads:[~2025-09-01 11:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26 10:18 [PATCH] iio: dac: use int instead of u32 to store error codes Qianfeng Rong
2025-08-26 13:42 ` David Lechner
2025-08-31 15:27 ` Jonathan Cameron
2025-09-01 11:55   ` Qianfeng Rong [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=7a775ae7-5925-4d64-a030-eeaa9d5809c9@vivo.com \
    --to=rongqianfeng@vivo.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --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=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