From: Jonathan Cameron <jic23@kernel.org>
To: Qianfeng Rong <rongqianfeng@vivo.com>
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>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
linux-iio@vger.kernel.org (open list:IIO SUBSYSTEM AND DRIVERS),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH v2 0/2] iio: use int type to store negative error codes
Date: Mon, 1 Sep 2025 17:40:06 +0100 [thread overview]
Message-ID: <20250901174006.11bf48a8@jic23-huawei> (raw)
In-Reply-To: <20250901135726.17601-1-rongqianfeng@vivo.com>
On Mon, 1 Sep 2025 21:57:24 +0800
Qianfeng Rong <rongqianfeng@vivo.com> wrote:
> Use int instead of unsigned int for 'ret' variable in ad5360_update_ctrl()
> and ad5421_update_ctrl() to store negative error codes or zero returned by
> other functions.
>
> Signed-off-by: Qianfeng Rong <rongqianfeng@vivo.com>
> ---
> v2: Split each driver into a separate patch.
Thanks for doing that.
Applied to the fixes-togreg branch of iio.git and marked for stable inclusion.
Thanks,
Jonathan
> ---
> Qianfeng Rong (2):
> iio: dac: ad5360: use int type to store negative error codes
> iio: dac: ad5421: use int type to store negative error codes
>
> drivers/iio/dac/ad5360.c | 2 +-
> drivers/iio/dac/ad5421.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
prev parent reply other threads:[~2025-09-01 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 13:57 [PATCH v2 0/2] iio: use int type to store negative error codes Qianfeng Rong
2025-09-01 13:57 ` [PATCH v2 1/2] iio: dac: ad5360: " Qianfeng Rong
2025-09-01 13:57 ` [PATCH v2 2/2] iio: dac: ad5421: " Qianfeng Rong
2025-09-01 15:46 ` [PATCH v2 0/2] iio: " Andy Shevchenko
2025-09-01 16:40 ` Jonathan Cameron [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=20250901174006.11bf48a8@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gregkh@suse.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=rongqianfeng@vivo.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