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.6
Date: Fri, 28 Jul 2023 14:01:51 +0200 [thread overview]
Message-ID: <cover.1690545605.git.geert+renesas@glider.be> (raw)
Hi Linus,
The following changes since commit bfc374a145ae133613e05b9b89be561f169cb58d:
pinctrl: renesas: rzg2l: Handle non-unique subnode names (2023-07-10 10:00:27 +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.6-tag1
for you to fetch changes up to 95eb19869401850f069723b296170b8b3bd5be9e:
pinctrl: renesas: rzg2l: Use devm_clk_get_enabled() helper (2023-07-25 12:28:45 +0200)
----------------------------------------------------------------
pinctrl: renesas: Updates for v6.6
- Use the new devm_clk_get_enabled() helper.
Thanks for pulling!
----------------------------------------------------------------
Christophe JAILLET (1):
pinctrl: renesas: rzg2l: Use devm_clk_get_enabled() helper
Geert Uytterhoeven (1):
pinctrl: renesas: rzv2m: Use devm_clk_get_enabled() helper
drivers/pinctrl/renesas/pinctrl-rzg2l.c | 32 +++++---------------------------
drivers/pinctrl/renesas/pinctrl-rzv2m.c | 32 +++++---------------------------
2 files changed, 10 insertions(+), 54 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:[~2023-07-28 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 12:01 Geert Uytterhoeven [this message]
2023-08-02 23:14 ` [GIT PULL] pinctrl: renesas: Updates for v6.6 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.1690545605.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).