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] arm64: dts: renesas: v3msk: add EtherAVB pins
Date: Mon, 26 Mar 2018 18:02:00 +0200 [thread overview]
Message-ID: <20180326160200.ke76bz2rltvveml7@verge.net.au> (raw)
In-Reply-To: <73ffe546-d7c5-ced6-d75b-be36f2457067@cogentembedded.com>
On Mon, Mar 26, 2018 at 06:27:06PM +0300, Sergei Shtylyov wrote:
> On 03/26/2018 12:01 PM, Simon Horman wrote:
>
> >> Add the (previously omitted) EtherAVB pin data to the V3M Starter Kit
> >> board's device tree.
> >>
> >> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> >>
> >> ---
> >> The patch is against the 'renesas-devel-20180314-v4.16-rc5' tag of Simon's
> >> 'renesas.git repo. It depends on the R8A77970 PFC driver patch adding EtherAVB
> >> pin groups (posted yesterday) in order to work properly...
> >
> > Thanks, I have marked this as deferred, please either:
> > * repost or ping me once the dependency is in an RC release or;
> > * let me know that its safe to apply this change - that is, it won't cause
> > a regression - without the dependency
>
> I'm seeing this patch merged under the today's devel tag -- please undo the merge
> as the PFC pre-requisite patch haven't hit Linus' repo yet.
Sorry about that. I have dropped the patch and pushed
renesas-devel-20180326v2-v4.16-rc7.
next prev parent reply other threads:[~2018-03-26 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 20:30 [PATCH] arm64: dts: renesas: v3msk: add EtherAVB pins Sergei Shtylyov
2018-03-26 9:01 ` Simon Horman
2018-03-26 15:27 ` Sergei Shtylyov
2018-03-26 16:02 ` Simon Horman [this message]
2018-04-20 11:28 ` Sergei Shtylyov
2018-04-24 9:18 ` 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=20180326160200.ke76bz2rltvveml7@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).