From: Marek Vasut <marek.vasut@mailbox.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>,
Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
huybui2 <huy.bui.wm@renesas.com>
Subject: Re: [PATCH 3/5] pinctrl: renesas: r8a779g0: Remove STPWT_EXTFXR
Date: Tue, 4 Nov 2025 22:28:12 +0100 [thread overview]
Message-ID: <428a59e8-2c18-4bf1-841d-3ead2c2c1cb0@mailbox.org> (raw)
In-Reply-To: <f6cfdbbc024d85e87583a1d57ea01582632f1216.1762274384.git.geert+renesas@glider.be>
On 11/4/25 5:59 PM, Geert Uytterhoeven wrote:
> From: huybui2 <huy.bui.wm@renesas.com>
>
> Rev.1.30 of the R-Car V4H Series Hardware User’s Manual removed the
> "STPWT_EXTFXR" signal from the pin control register tables. As this is
> further unused in the pin control driver, it can be removed safely.
>
> Signed-off-by: huybui2 <huy.bui.wm@renesas.com>
The real name is 'Huy Bui' instead of huybui2 login name.
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
Also, matches U-Boot patch, thanks !
next prev parent reply other threads:[~2025-11-04 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 16:59 [PATCH 0/5] pinctrl: renesas: rcar-v4x: Remove removed signals Geert Uytterhoeven
2025-11-04 16:59 ` [PATCH 1/5] pinctrl: renesas: r8a779g0: Remove AVB[01]_MII Geert Uytterhoeven
2025-11-04 21:32 ` Marek Vasut
2025-11-04 16:59 ` [PATCH 2/5] pinctrl: renesas: r8a779g0: Remove CC5_OSCOUT Geert Uytterhoeven
2025-11-04 21:27 ` Marek Vasut
2025-11-05 8:34 ` Geert Uytterhoeven
2025-11-04 16:59 ` [PATCH 3/5] pinctrl: renesas: r8a779g0: Remove STPWT_EXTFXR Geert Uytterhoeven
2025-11-04 21:28 ` Marek Vasut [this message]
2025-11-04 16:59 ` [PATCH 4/5] pinctrl: renesas: r8a779h0: Remove CC5_OSCOUT Geert Uytterhoeven
2025-11-04 21:28 ` Marek Vasut
2025-11-04 16:59 ` [PATCH 5/5] pinctrl: renesas: r8a779h0: Remove STPWT_EXTFXR Geert Uytterhoeven
2025-11-04 21:29 ` Marek Vasut
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=428a59e8-2c18-4bf1-841d-3ead2c2c1cb0@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=geert+renesas@glider.be \
--cc=huy.bui.wm@renesas.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@mailbox.org \
/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).