From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [GIT PULL] pinctrl: renesas: Updates for v6.19
Date: Fri, 31 Oct 2025 11:44:05 +0100 [thread overview]
Message-ID: <cover.1761906880.git.geert+renesas@glider.be> (raw)
Hi Linus,
The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git tags/renesas-pinctrl-for-v6.19-tag1
for you to fetch changes up to a5fad3aeff41f89ac94230d66ee5f9c1526cb3ce:
pinctrl: renesas: rzg2l: Remove useless wrappers (2025-10-27 11:53:27 +0100)
----------------------------------------------------------------
pinctrl: renesas: Updates for v6.19
- Fix interrupt configuration and port mode after resume on RZ/G2L
family SoCs,
- Miscellaneous fixes and improvements.
Thanks for pulling!
----------------------------------------------------------------
Biju Das (2):
pinctrl: renesas: rzg2l: Drop unnecessary pin configurations
pinctrl: renesas: rzg2l: Fix PMC restore
Claudiu Beznea (1):
pinctrl: renesas: rzg2l: Fix ISEL restore on resume
Cosmin Tanislav (2):
pinctrl: renesas: rzg2l: Remove extra semicolons
pinctrl: renesas: rzg2l: Remove useless wrappers
Geert Uytterhoeven (2):
pinctrl: renesas: Remove unneeded semicolons
pinctrl: renesas: rza1: Make mux_conf const in rza1_pin_mux_single()
Marek Vasut (1):
pinctrl: renesas: Drop duplicate newlines
drivers/pinctrl/renesas/pfc-emev2.c | 1 -
drivers/pinctrl/renesas/pfc-r8a73a4.c | 2 -
drivers/pinctrl/renesas/pfc-r8a7778.c | 1 -
drivers/pinctrl/renesas/pfc-r8a77951.c | 1 -
drivers/pinctrl/renesas/pfc-r8a7796.c | 1 -
drivers/pinctrl/renesas/pfc-r8a77965.c | 1 -
drivers/pinctrl/renesas/pfc-r8a77970.c | 1 -
drivers/pinctrl/renesas/pfc-r8a77980.c | 1 -
drivers/pinctrl/renesas/pfc-r8a77995.c | 2 -
drivers/pinctrl/renesas/pfc-r8a779f0.c | 1 -
drivers/pinctrl/renesas/pfc-r8a779h0.c | 1 -
drivers/pinctrl/renesas/pfc-sh7723.c | 1 -
drivers/pinctrl/renesas/pfc-sh7724.c | 1 -
drivers/pinctrl/renesas/pfc-sh7734.c | 1 -
drivers/pinctrl/renesas/pinctrl-rza1.c | 7 +-
drivers/pinctrl/renesas/pinctrl-rzg2l.c | 122 +++++++++++++++++++-------------
drivers/pinctrl/renesas/pinctrl-rzt2h.c | 4 +-
drivers/pinctrl/renesas/pinctrl-rzv2m.c | 10 +--
18 files changed, 83 insertions(+), 76 deletions(-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2025-10-31 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 10:44 Geert Uytterhoeven [this message]
2025-11-09 22:55 ` [GIT PULL] pinctrl: renesas: Updates for v6.19 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=cover.1761906880.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.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).