From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>,
Simon Horman <horms@verge.net.au>
Cc: Rob Herring <robh+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Add R8A77970/Eagle PFC support
Date: Mon, 12 Feb 2018 21:04:06 +0300 [thread overview]
Message-ID: <19d23fa2-1205-89a0-786f-f301ca7a0f7b@cogentembedded.com> (raw)
In-Reply-To: <049b0a0a-b1c2-73e6-c471-ca8342bba6ab@ideasonboard.com>
On 01/19/2018 01:48 PM, Kieran Bingham wrote:
>>> Here's the set of 3 patches against Simon Horman's 'renesas.git' repo's
>>> 'renesas-devel-20171110-v4.14-rc8' tag. We're adding the R8A77970 PFC node
>>> and then describing the pins for SCIF0 and EtherAVB devices declared earlier.
>>> These patches depend on the R8A77970 PFC suport in order to work properly.
>>>
>>> [1/3] arm64: dts: renesas: r8a77970: add PFC support
>>> [2/3] arm64: dts: renesas: eagle: add SCIF0 pins
>>> [3/3] arm64: dts: renesas: eagle: add EtherAVB pins
>>
>> Hi Sergei,
>>
>> I have marked these patches as deferred pending acceptance of the PFC
>> driver. Please repost or otherwise ping me once that dependency has been
>> accepted.
>
> Has the dependency blocking this series been resolved yet ?
Now it is, except for the 3rd patch... Simon, do I need to repost the first two?
The 1st one did apply to 4.16-rc1 here with a fuzz...
> (I have patches for the Eagle-V3M which are blocked waiting for the PFC support)
>
> --
> Regards
>
> Kieran
MBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Add R8A77970/Eagle PFC support
Date: Mon, 12 Feb 2018 21:04:06 +0300 [thread overview]
Message-ID: <19d23fa2-1205-89a0-786f-f301ca7a0f7b@cogentembedded.com> (raw)
In-Reply-To: <049b0a0a-b1c2-73e6-c471-ca8342bba6ab@ideasonboard.com>
On 01/19/2018 01:48 PM, Kieran Bingham wrote:
>>> Here's the set of 3 patches against Simon Horman's 'renesas.git' repo's
>>> 'renesas-devel-20171110-v4.14-rc8' tag. We're adding the R8A77970 PFC node
>>> and then describing the pins for SCIF0 and EtherAVB devices declared earlier.
>>> These patches depend on the R8A77970 PFC suport in order to work properly.
>>>
>>> [1/3] arm64: dts: renesas: r8a77970: add PFC support
>>> [2/3] arm64: dts: renesas: eagle: add SCIF0 pins
>>> [3/3] arm64: dts: renesas: eagle: add EtherAVB pins
>>
>> Hi Sergei,
>>
>> I have marked these patches as deferred pending acceptance of the PFC
>> driver. Please repost or otherwise ping me once that dependency has been
>> accepted.
>
> Has the dependency blocking this series been resolved yet ?
Now it is, except for the 3rd patch... Simon, do I need to repost the first two?
The 1st one did apply to 4.16-rc1 here with a fuzz...
> (I have patches for the Eagle-V3M which are blocked waiting for the PFC support)
>
> --
> Regards
>
> Kieran
MBR, Sergei
next prev parent reply other threads:[~2018-02-12 18:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 20:02 [PATCH 0/3] Add R8A77970/Eagle PFC support Sergei Shtylyov
2017-11-10 20:02 ` Sergei Shtylyov
2017-11-10 20:02 ` Sergei Shtylyov
[not found] ` <20171110200218.747996672-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2017-11-13 7:53 ` Simon Horman
2017-11-13 7:53 ` Simon Horman
2017-11-13 7:53 ` Simon Horman
2018-01-19 10:48 ` Kieran Bingham
2018-01-19 10:48 ` Kieran Bingham
2018-02-12 18:04 ` Sergei Shtylyov [this message]
2018-02-12 18:04 ` Sergei Shtylyov
2018-02-13 7:52 ` Simon Horman
2018-02-13 7:52 ` Simon Horman
2018-02-13 10:46 ` Sergei Shtylyov
2018-02-13 10:46 ` Sergei Shtylyov
2018-02-13 11:40 ` Simon Horman
2018-02-13 11:40 ` Simon Horman
-- strict thread matches above, loose matches on Subject: below --
2017-11-10 20:02 Sergei Shtylyov
2017-11-10 20:02 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=19d23fa2-1205-89a0-786f-f301ca7a0f7b@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=kieran.bingham@ideasonboard.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.