From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Cao Van Dong <cv-dong@jinso.co.jp>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 3/4] pinctrl: sh-pfc: r8a7796: Add TPU pins, groups and functions
Date: Tue, 7 May 2019 16:54:18 +0200 [thread overview]
Message-ID: <CAMuHMdVwsghkR22QBfZTBswsr8sSQvoEiiRmEO22Wevqpzp6Pg@mail.gmail.com> (raw)
In-Reply-To: <20190503094926.12208-4-geert+renesas@glider.be>
On Fri, May 3, 2019 at 11:49 AM Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
> Add pins, groups and functions for the 16-Bit Timer Pulse Unit outputs
> on the R-Car M3-W and RZ/G2M SoCs.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/pinctrl/sh-pfc/pfc-r8a7796.c | 42 ++++++++++++++++++++++++++++
This is embarrassing: how did I manage to forget to update the .common[]
array sizes, given I added all this extra validation code?!?
Sorry for that. stay tuned for v2...
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 prev parent reply other threads:[~2019-05-07 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 9:49 [PATCH 0/4] pinctrl: sh-pfc: r8a7795/6/65: Add TPU pins, groups and functions Geert Uytterhoeven
2019-05-03 9:49 ` [PATCH 1/4] pinctrl: sh-pfc: r8a7795-es1: " Geert Uytterhoeven
2019-05-03 9:49 ` [PATCH 2/4] pinctrl: sh-pfc: r8a7795: " Geert Uytterhoeven
2019-05-03 9:49 ` [PATCH 3/4] pinctrl: sh-pfc: r8a7796: " Geert Uytterhoeven
2019-05-07 14:54 ` Geert Uytterhoeven [this message]
2019-05-03 9:49 ` [PATCH 4/4] pinctrl: sh-pfc: r8a77965: " 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=CAMuHMdVwsghkR22QBfZTBswsr8sSQvoEiiRmEO22Wevqpzp6Pg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=cv-dong@jinso.co.jp \
--cc=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).