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: sh-pfc: Updates for v5.8 (take two+)
Date: Wed, 20 May 2020 16:04:30 +0200 [thread overview]
Message-ID: <20200520140430.13933-1-geert+renesas@glider.be> (raw)
Hi Linus,
[ This time with a correct SoC name in the description, thanks Sergei! ]
The following changes since commit 41fe32ecc7aff4527a4ee477870d9b1164be95a4:
MAINTAINERS: Add DT Bindings for Renesas Pin Function Controllers (2020-04-20 13:14:05 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git tags/sh-pfc-for-v5.8-tag2
for you to fetch changes up to dfae0422de12265ae7c9bf57b34990200dea0c83:
MAINTAINERS: Renesas Pin Controllers are supported (2020-05-20 14:02:00 +0200)
----------------------------------------------------------------
pinctrl: sh-pfc: Updates for v5.8 (take two)
- Add support for the new RZ/G1H (r8a7742) SoC,
- Minor fixes and improvements.
Thanks for pulling!
----------------------------------------------------------------
Geert Uytterhoeven (2):
pinctrl: rza1: Fix flag name in comment
MAINTAINERS: Renesas Pin Controllers are supported
Lad Prabhakar (2):
dt-bindings: pinctrl: sh-pfc: Document r8a7742 PFC support
pinctrl: sh-pfc: r8a7790: Add r8a7742 PFC support
.../bindings/pinctrl/renesas,pfc-pinctrl.txt | 1 +
MAINTAINERS | 2 +-
drivers/pinctrl/pinctrl-rza1.c | 2 +-
drivers/pinctrl/sh-pfc/Kconfig | 4 +
drivers/pinctrl/sh-pfc/Makefile | 1 +
drivers/pinctrl/sh-pfc/core.c | 6 +
drivers/pinctrl/sh-pfc/pfc-r8a7790.c | 744 +++++++++++----------
drivers/pinctrl/sh-pfc/sh_pfc.h | 1 +
8 files changed, 407 insertions(+), 354 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:[~2020-05-20 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 14:04 Geert Uytterhoeven [this message]
2020-05-25 9:20 ` [GIT PULL] pinctrl: sh-pfc: Updates for v5.8 (take two+) Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2020-05-20 12:53 [GIT PULL] pinctrl: sh-pfc: Updates for v5.8 (take two) Geert Uytterhoeven
2020-05-20 13:47 ` Sergei Shtylyov
2020-05-20 14:05 ` Geert Uytterhoeven
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=20200520140430.13933-1-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).