From: Simon Horman <horms@verge.net.au>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-renesas-soc@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Add R8A77980/Condor PFC support
Date: Tue, 13 Mar 2018 19:46:12 +0100 [thread overview]
Message-ID: <20180313184612.e4z3dkmsjbmnh252@verge.net.au> (raw)
In-Reply-To: <88e52531-e538-8685-110a-1a2e79a3fe49@cogentembedded.com>
On Fri, Mar 09, 2018 at 03:04:56PM +0300, Sergei Shtylyov wrote:
> Hello!
>
> Here's the set of 3 patches against Simon Horman's 'renesas.git' repo's
> 'renesas-devel-20180308-v4.16-rc4' tag. We're adding the R8A77980 PFC node
> and then describing the pins for SCIF0 and EtherAVB devices declared earlier.
> These patches depend on the R8A77980 PFC support in order to work properly.
I have marked these patches as Deferred. Please repost or ping me
once the dependencies are in an RC release. If looser dependency handling
is appropriate please let me know.
next prev parent reply other threads:[~2018-03-13 18:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 12:04 [PATCH 0/3] Add R8A77980/Condor PFC support Sergei Shtylyov
2018-03-09 12:06 ` [PATCH 1/3] arm64: dts: renesas: r8a77980: add " Sergei Shtylyov
2018-03-09 12:36 ` Geert Uytterhoeven
2018-03-09 12:07 ` [PATCH 2/3] arm64: dts: renesas: condor: add SCIF0 pins Sergei Shtylyov
2018-03-09 12:39 ` Geert Uytterhoeven
2018-03-09 12:09 ` [PATCH 3/3] arm64: dts: renesas: condor: add EtherAVB pins Sergei Shtylyov
2018-03-09 12:44 ` Geert Uytterhoeven
2018-03-09 17:26 ` Sergei Shtylyov
2018-03-13 18:46 ` Simon Horman [this message]
2018-04-20 17:33 ` [PATCH 0/3] Add R8A77980/Condor PFC support Sergei Shtylyov
2018-04-24 9:20 ` 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=20180313184612.e4z3dkmsjbmnh252@verge.net.au \
--to=horms@verge.net.au \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=will.deacon@arm.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).