From: Linus Walleij <linus.walleij@linaro.org>
To: Magnus Damm <magnus.damm@gmail.com>, geert@glider.be
Cc: "linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
koji.matsuoka.xm@renesas.com,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH 01/04] pinctrl: sh-pfc: r8a7794: Add DU pin groups
Date: Sun, 29 Nov 2015 22:25:33 +0100 [thread overview]
Message-ID: <CACRpkdZLnBAwYNzCP5=LP1B6+VEUfLkCW-tSQe09soTqwU19jw@mail.gmail.com> (raw)
In-Reply-To: <20151117031841.24924.27388.sendpatchset@little-apple>
On Tue, Nov 17, 2015 at 4:18 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
> From: Koji Matsuoka <koji.matsuoka.xm@renesas.com>
>
> r8a7794 PFC DU support from the R-Car Gen2 v1.9.4 BSP
>
> Signed-off-by: Koji Matsuoka <koji.matsuoka.xm@renesas.com>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
Acked-by for all from my side, Geert, I expect that you
queue these with the rest of the SH PFC stuff.
Yours,
Linus Walleij
next prev parent reply other threads:[~2015-11-29 21:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 3:18 [PATCH 00/04] pinctrl: sh-pfc: r8a7794: DU support Magnus Damm
2015-11-17 3:18 ` [PATCH 01/04] pinctrl: sh-pfc: r8a7794: Add DU pin groups Magnus Damm
2015-11-29 21:25 ` Linus Walleij [this message]
2015-11-30 8:53 ` Geert Uytterhoeven
2015-11-17 3:18 ` [PATCH 02/04] pinctrl: sh-pfc: r8a7794: Separate DU CDE and DISP Magnus Damm
2015-11-17 3:19 ` [PATCH 03/04] pinctrl: sh-pfc: r8a7794: Add missing dot clock signals Magnus Damm
2015-12-21 22:01 ` Sergei Shtylyov
2015-11-17 3:19 ` [PATCH 04/04] pinctrl: sh-pfc: r8a7794: Break out ODDF from sync Magnus Damm
2015-11-20 2:46 ` [PATCH 00/04] pinctrl: sh-pfc: r8a7794: DU support Laurent Pinchart
2015-11-20 7:16 ` Magnus Damm
2015-11-20 14:53 ` Laurent Pinchart
2015-11-25 0:16 ` Simon Horman
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='CACRpkdZLnBAwYNzCP5=LP1B6+VEUfLkCW-tSQe09soTqwU19jw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=geert@glider.be \
--cc=horms@verge.net.au \
--cc=koji.matsuoka.xm@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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).