From: Simon Horman <horms@verge.net.au>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/3] Add R8A7743/SK-RZG1M PFC support
Date: Wed, 5 Jul 2017 11:33:08 +0100 [thread overview]
Message-ID: <20170705103308.GA29876@verge.net.au> (raw)
In-Reply-To: <20170424061217.GC14843@verge.net.au>
On Mon, Apr 24, 2017 at 08:12:18AM +0200, Simon Horman wrote:
> On Thu, Apr 20, 2017 at 09:51:32PM +0300, Sergei Shtylyov wrote:
> > Hello.
> >
> > Here's the set of 3 patches against Simon Horman's 'renesas.git' repo,
> > 'renesas-devel-20170420-v4.11-rc7' tag. We're adding the R8A7743 PFC node
> > and then describing the pins for SCIF0 and Ether devices declared earlier.
> > These patches depend on the R8A7743 PFC suport in order to work properly.
>
> Thanks. I have marked these as deferred pending acceptance of the PFC
> driver changes. Please repost or otherwise let me know when dependency
> is satisfied.
It appears that the driver changes have been acceptedi[1] so
I have queued these up for v4.14.
[1] https://www.mail-archive.com/linux-renesas-soc@vger.kernel.org/msg15744.html
next prev parent reply other threads:[~2017-07-05 10:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 18:51 [PATCH v2 0/3] Add R8A7743/SK-RZG1M PFC support Sergei Shtylyov
2017-04-24 6:12 ` Simon Horman
2017-06-07 16:16 ` Sergei Shtylyov
2017-06-07 17:52 ` Geert Uytterhoeven
2017-06-08 12:53 ` Sergei Shtylyov
2017-07-05 10:33 ` Simon Horman [this message]
[not found] ` <20170705103308.GA29876-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2017-07-05 12:06 ` Sergei Shtylyov
2017-07-05 13:10 ` Simon Horman
-- strict thread matches above, loose matches on Subject: below --
2017-04-20 18:51 Sergei Shtylyov
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=20170705103308.GA29876@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).