From: Linus Walleij <linus.walleij@linaro.org>
To: Qianfeng Rong <rongqianfeng@vivo.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
"moderated list:ARM/Marvell Kirkwood and Armada 370, 375,
38x,..." <linux-arm-kernel@lists.infradead.org>,
"open list:PIN CONTROL SUBSYSTEM" <linux-gpio@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] pinctrl: armada-37xx: Use int type to store negative error codes
Date: Mon, 1 Sep 2025 15:11:25 +0200 [thread overview]
Message-ID: <CACRpkdY14ZuAp+mg==M62draaaf897Ry-Nkh93UR132iUqnLvw@mail.gmail.com> (raw)
In-Reply-To: <20250831084958.431913-2-rongqianfeng@vivo.com>
On Sun, Aug 31, 2025 at 10:50 AM Qianfeng Rong <rongqianfeng@vivo.com> wrote:
> In armada_37xx_gpio_direction_output(), the 'ret' variable might store
> the negative error codes returned by regmap_update_bits(), and in
> armada_37xx_edge_both_irq_swap_pol(), the 'ret' variable directly
> stores -1, so the type of the 'ret' variable needs to be changed to
> int in both cases.
>
> No effect on runtime.
>
> Signed-off-by: Qianfeng Rong <rongqianfeng@vivo.com>
This patch (1/3) applied for next in the pinctrl tree.
Yours,
Linus Walleij
next prev parent reply other threads:[~2025-09-01 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 8:49 [PATCH 0/3] pinctrl: Use int type to store negative error codes Qianfeng Rong
2025-08-31 8:49 ` [PATCH 1/3] pinctrl: armada-37xx: " Qianfeng Rong
2025-08-31 14:41 ` Andrew Lunn
2025-09-01 13:11 ` Linus Walleij [this message]
2025-08-31 8:49 ` [PATCH 2/3] pinctrl: ma35: " Qianfeng Rong
2025-09-01 13:11 ` Linus Walleij
2025-08-31 8:49 ` [PATCH 3/3] pinctrl: renesas: " Qianfeng Rong
2025-09-01 9:07 ` Geert Uytterhoeven
2025-09-01 10:13 ` Qianfeng Rong
2025-09-01 10:25 ` Geert Uytterhoeven
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='CACRpkdY14ZuAp+mg==M62draaaf897Ry-Nkh93UR132iUqnLvw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andrew@lunn.ch \
--cc=brgl@bgdev.pl \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rongqianfeng@vivo.com \
--cc=sebastian.hesselbarth@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;
as well as URLs for NNTP newsgroup(s).