From: Jakub Kicinski <kuba@kernel.org>
To: Phil Edworthy <phil.edworthy@renesas.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Sergey Shtylyov <s.shtylyov@omp.ru>,
Sergei Shtylyov <sergei.shtylyov@gmail.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
linux-clk@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 0/9] Add Renesas RZ/V2M Ethernet support
Date: Wed, 4 May 2022 17:57:57 -0700 [thread overview]
Message-ID: <20220504175757.0a3c1a6a@kernel.org> (raw)
In-Reply-To: <20220504145454.71287-1-phil.edworthy@renesas.com>
On Wed, 4 May 2022 15:54:45 +0100 Phil Edworthy wrote:
> The RZ/V2M Ethernet is very similar to R-Car Gen3 Ethernet-AVB, though
> some small parts are the same as R-Car Gen2.
> Other differences are:
> * It has separate data (DI), error (Line 1) and management (Line 2) irqs
> rather than one irq for all three.
> * Instead of using the High-speed peripheral bus clock for gPTP, it has
> a separate gPTP reference clock.
>
> The dts patches depend on v4 of the following patch set:
> "Add new Renesas RZ/V2M SoC and Renesas RZ/V2M EVK support"
>
> Phil Edworthy (9):
> clk: renesas: r9a09g011: Add eth clock and reset entries
> dt-bindings: net: renesas,etheravb: Document RZ/V2M SoC
> ravb: Separate use of GIC reg for PTME from multi_irqs
> ravb: Separate handling of irq enable/disable regs into feature
> ravb: Support separate Line0 (Desc), Line1 (Err) and Line2 (Mgmt) irqs
> ravb: Use separate clock for gPTP
> ravb: Add support for RZ/V2M
> arm64: dts: renesas: r9a09g011: Add ethernet nodes
> arm64: dts: renesas: rzv2m evk: Enable ethernet
How are you expecting this to be merged?
I think you should drop the first (clk) patch from this series
so we can apply the series to net-next. And route the clk patch
thru Geert's tree separately?
Right now patchwork thinks the series is incomplete because it
hasn't received patch 1.
next prev parent reply other threads:[~2022-05-05 0:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 14:54 [PATCH 0/9] Add Renesas RZ/V2M Ethernet support Phil Edworthy
2022-05-04 14:54 ` [PATCH 1/9] clk: renesas: r9a09g011: Add eth clock and reset entries Phil Edworthy
2022-05-05 9:19 ` Geert Uytterhoeven
2022-05-04 14:54 ` [PATCH 2/9] dt-bindings: net: renesas,etheravb: Document RZ/V2M SoC Phil Edworthy
2022-05-07 18:21 ` Sergey Shtylyov
2022-05-09 8:15 ` Phil Edworthy
2022-05-04 14:54 ` [PATCH 3/9] ravb: Separate use of GIC reg for PTME from multi_irqs Phil Edworthy
2022-05-04 20:40 ` Sergey Shtylyov
2022-05-05 8:26 ` Phil Edworthy
2022-05-04 14:54 ` [PATCH 4/9] ravb: Separate handling of irq enable/disable regs into feature Phil Edworthy
2022-05-04 19:54 ` Sergey Shtylyov
2022-05-05 8:12 ` Phil Edworthy
2022-05-04 14:54 ` [PATCH 5/9] ravb: Support separate Line0 (Desc), Line1 (Err) and Line2 (Mgmt) irqs Phil Edworthy
2022-05-05 19:40 ` Sergey Shtylyov
2022-05-09 8:00 ` Phil Edworthy
2022-05-04 14:54 ` [PATCH 6/9] ravb: Use separate clock for gPTP Phil Edworthy
2022-05-05 18:13 ` Sergey Shtylyov
2022-05-04 14:54 ` [PATCH 7/9] ravb: Add support for RZ/V2M Phil Edworthy
2022-05-05 20:18 ` Sergey Shtylyov
2022-05-09 7:01 ` Phil Edworthy
2022-05-04 14:54 ` [PATCH 8/9] arm64: dts: renesas: r9a09g011: Add ethernet nodes Phil Edworthy
2022-05-04 14:54 ` [PATCH 9/9] arm64: dts: renesas: rzv2m evk: Enable ethernet Phil Edworthy
2022-05-05 0:57 ` Jakub Kicinski [this message]
2022-05-05 6:59 ` [PATCH 0/9] Add Renesas RZ/V2M Ethernet support Geert Uytterhoeven
2022-05-05 9:14 ` Phil Edworthy
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=20220504175757.0a3c1a6a@kernel.org \
--to=kuba@kernel.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phil.edworthy@renesas.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=s.shtylyov@omp.ru \
--cc=sboyd@kernel.org \
--cc=sergei.shtylyov@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 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.