From: Linus Walleij <linus.walleij@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Takeshi Kihara <takeshi.kihara.df@renesas.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 0/5] pinctrl: sh-pfc: r8a7795: (H)SCIF Updates
Date: Fri, 25 Sep 2015 16:07:27 +0000 [thread overview]
Message-ID: <CACRpkdZTp0zCowusWNPXGLD=CstcbH-pGOnoSpg54n4xdSPMeg@mail.gmail.com> (raw)
In-Reply-To: <1440612144-16877-1-git-send-email-geert+renesas@glider.be>
On Wed, Aug 26, 2015 at 11:02 AM, Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
> This series contains (H)SCIF-related updates for the R-Car H3 (r8a7795)
> pin function controller driver:
> - Fixes and updates for SCIF pindata (incl. a DTS update),
> - Addition of HSCIF support.
>
> This is against "[PATCH] pinctrl: sh-pfc: Add R8A7795 PFC support" and
> the current state (sic) of the Salvator-X DTS.
The series:
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
prev parent reply other threads:[~2015-09-25 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 18:02 [PATCH 0/5] pinctrl: sh-pfc: r8a7795: (H)SCIF Updates Geert Uytterhoeven
2015-08-26 18:02 ` [PATCH 1/5] pinctrl: sh-pfc: r8a7795: Fix and extend SCIF0 pin data Geert Uytterhoeven
2015-08-26 18:02 ` [PATCH 2/5] pinctrl: sh-pfc: r8a7795: Extend SCIF2 " Geert Uytterhoeven
2015-08-26 18:02 ` [PATCH 3/5] pinctrl: sh-pfc: r8a7795: Fix SCIF5 " Geert Uytterhoeven
2015-08-26 18:02 ` [PATCH 4/5] pinctrl: sh-pfc: r8a7795: Add HSCIF pins, groups, and functions Geert Uytterhoeven
2015-08-26 18:02 ` [PATCH 5/5] arm64: renesas: salvator-x: Update SCIF2 pin group Geert Uytterhoeven
2015-09-25 16:07 ` Linus Walleij [this message]
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='CACRpkdZTp0zCowusWNPXGLD=CstcbH-pGOnoSpg54n4xdSPMeg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=takeshi.kihara.df@renesas.com \
/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).