From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Linus Walleij <linusw@kernel.org>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Sean Wang <sean.wang@kernel.org>,
Paul Cercueil <paul@crapouillou.net>,
Tony Lindgren <tony@atomide.com>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
linux-gpio@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 3/7] pinctrl: ingenic: Fix type in .pin_config_group_get() callback
Date: Sat, 2 May 2026 16:48:21 +0200 [thread overview]
Message-ID: <98F0E379-88A0-414E-B24A-187374E5FCAD@goldelico.com> (raw)
In-Reply-To: <9f50c234c44af9075b5252ee7e59452ed2179b27.1777562725.git.geert+renesas@glider.be>
> Am 30.04.2026 um 17:33 schrieb Geert Uytterhoeven <geert+renesas@glider.be>:
>
> On 64-bit platforms, "unsigned long" is 64-bit. Hence checking if all
> "unsigned long" configuration values are equal should be done using an
> "unsigned long" temporary.
>
> While Ingenic is a 32-bit platform, it is still better to use the
> correct type, to serve as an example.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
tested to show no visible difference on Ingenic X1600 based board (Letux X16) on top of v7.1-rc1.
BR and thanks,
Nikolaus
next prev parent reply other threads:[~2026-05-02 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 15:33 [PATCH 0/7] pinctrl: Fix types in .pin_config_group_get() callbacks Geert Uytterhoeven
2026-04-30 15:33 ` [PATCH 1/7] pinctrl: airoha: Fix type in .pin_config_group_get() callback Geert Uytterhoeven
2026-04-30 15:33 ` [PATCH 2/7] pinctrl: equilibrium: " Geert Uytterhoeven
2026-04-30 15:33 ` [PATCH 3/7] pinctrl: ingenic: " Geert Uytterhoeven
2026-05-02 14:48 ` H. Nikolaus Schaller [this message]
2026-05-04 10:26 ` Paul Cercueil
2026-04-30 15:33 ` [PATCH 4/7] pinctrl: mediatek: moore: " Geert Uytterhoeven
2026-04-30 15:33 ` [PATCH 5/7] pinctrl: renesas: rzg2l: " Geert Uytterhoeven
2026-05-05 10:48 ` Prabhakar Mahadev Lad
2026-04-30 15:33 ` [PATCH 6/7] pinctrl: renesas: rzv2m: " Geert Uytterhoeven
2026-04-30 15:33 ` [PATCH 7/7] pinctrl: single: " Geert Uytterhoeven
2026-05-05 10:45 ` [PATCH 0/7] pinctrl: Fix types in .pin_config_group_get() callbacks Linus Walleij
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=98F0E379-88A0-414E-B24A-187374E5FCAD@goldelico.com \
--to=hns@goldelico.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=geert+renesas@glider.be \
--cc=haojian.zhuang@linaro.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=paul@crapouillou.net \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=sean.wang@kernel.org \
--cc=tony@atomide.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 read-only IMAP folder(s) and NNTP newsgroup(s).