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.13 (take two)
Date: Mon, 4 Nov 2024 14:27:02 +0100 [thread overview]
Message-ID: <cover.1730726328.git.geert+renesas@glider.be> (raw)
Hi Linus,
The following changes since commit 5dcde519a067ac5c85c273e550dde1873e2199bf:
pinctrl: renesas: Select PINCTRL_RZG2L for RZ/V2H(P) SoC (2024-10-14 10:02:13 +0200)
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.13-tag2
for you to fetch changes up to f407af78c8d3b6035f81152b15ad67063f42514e:
pinctrl: renesas: rzg2l: Use gpiochip_populate_parent_fwspec_twocell helper (2024-10-25 10:43:18 +0200)
----------------------------------------------------------------
pinctrl: renesas: Updates for v6.13 (take two)
- Use the gpiochip_populate_parent_fwspec_twocell() helper.
Thanks for pulling!
----------------------------------------------------------------
Lad Prabhakar (1):
pinctrl: renesas: rzg2l: Use gpiochip_populate_parent_fwspec_twocell helper
drivers/pinctrl/renesas/pinctrl-rzg2l.c | 17 +----------------
1 file changed, 1 insertion(+), 16 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:[~2024-11-04 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 13:27 Geert Uytterhoeven [this message]
2024-11-05 9:51 ` [GIT PULL] pinctrl: renesas: Updates for v6.13 (take two) 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.1730726328.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).