From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Subject: Re: [PATCH v3 0/4] Initial r8a7796 PFC support
Date: Tue, 6 Sep 2016 12:44:21 +0200 [thread overview]
Message-ID: <20160906104420.GD16304@verge.net.au> (raw)
In-Reply-To: <CAMuHMdU3g6UF+4HUsDo806XQ9sv3QWe-zxGv0fu3jC3xrW_Bag@mail.gmail.com>
On Fri, Aug 19, 2016 at 11:17:51AM +0200, Geert Uytterhoeven wrote:
> Hi Ulrich,
>
> On Thu, Aug 18, 2016 at 3:12 PM, Ulrich Hecht
> <ulrich.hecht+renesas@gmail.com> wrote:
> > This implements a minimal set of PFC functionality for the M3 and sits on
> > top of renesas-drivers-2016-08-09-v4.8-rc1. It includes the SCIF pin groups
> > and enables pin control for the serial console (SCIF2) on the Salvator-X
> > board.
> >
> > This revision has scif_clk support, no bogus pin assignments, and enhanced
> > ePAPR compliance. See below for details.
>
> Thank you, I've applied the first two patches to sh-pfc-for-v4.9.
I have queued up the remaining two patches on a branch based on
the sh-pfc-for-v4.9-tag2 tag of Geert's tree.
prev parent reply other threads:[~2016-09-06 10:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 13:12 [PATCH v3 0/4] Initial r8a7796 PFC support Ulrich Hecht
2016-08-18 13:12 ` [PATCH v3 1/4] pinctrl: sh-pfc: Initial R8A7796 " Ulrich Hecht
2016-08-18 13:12 ` [PATCH v3 2/4] pinctrl: sh-pfc: r8a7796: Add SCIF pins, groups and functions Ulrich Hecht
2016-08-18 13:12 ` [PATCH v3 3/4] arm64: dts: r8a7796: Add pinctrl device node Ulrich Hecht
2016-08-18 13:12 ` [PATCH v3 4/4] arm64: dts: r8a7796: salvator: add serial console pins Ulrich Hecht
2016-08-19 7:30 ` Geert Uytterhoeven
2016-08-19 9:17 ` [PATCH v3 0/4] Initial r8a7796 PFC support Geert Uytterhoeven
2016-09-06 10:44 ` Simon Horman [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=20160906104420.GD16304@verge.net.au \
--to=horms@verge.net.au \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=ulrich.hecht+renesas@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