[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <TYCPR01MB593398E6E5422E81C01F1F8C86E59@TYCPR01MB5933.jpnprd01.prod.outlook.com>
Date: Fri, 23 Jul 2021 06:28:48 +0000
From: Biju Das <biju.das.jz@...renesas.com>
To: Andrew Lunn <andrew@...n.ch>,
Sergei Shtylyov <sergei.shtylyov@...il.com>
CC: "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Sergey Shtylyov <s.shtylyov@...russia.ru>,
Adam Ford <aford173@...il.com>,
Yuusuke Ashizuka <ashiduka@...itsu.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-renesas-soc@...r.kernel.org"
<linux-renesas-soc@...r.kernel.org>,
Chris Paterson <Chris.Paterson2@...esas.com>,
Biju Das <biju.das@...renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@...renesas.com>
Subject: RE: [PATCH net-next 00/18] Add Gigabit Ethernet driver support
Hi Andrew and Sergei,
> Subject: Re: [PATCH net-next 00/18] Add Gigabit Ethernet driver support
>
> On Thu, Jul 22, 2021 at 11:53:59PM +0300, Sergei Shtylyov wrote:
> > On 7/22/21 5:13 PM, Biju Das wrote:
> >
> > > The DMAC and EMAC blocks of Gigabit Ethernet IP is almost similar to
> Ethernet AVB.
> > >
> > > The Gigabit Etherner IP consists of Ethernet controller (E-MAC),
> Internal TCP/IP Offload Engine (TOE) and Dedicated Direct memory access
> controller (DMAC).
> > >
> > > With few changes in driver, we can support Gigabit ethernet driver as
> well.
> > >
> > > This patch series is aims to support the same
> > >
> > > RFC->V1
> > > * Incorporated feedback from Andrew, Sergei, Geert and Prabhakar
> > > *
> > > https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpa
> > > tchwork.kernel.org%2Fproject%2Flinux-renesas-soc%2Flist%2F%3Fseries%
> > > 3D515525&data=04%7C01%7Cbiju.das.jz%40bp.renesas.com%7C6fe3922cc
> > > 35d4178cb1d08d94d54bc75%7C53d82571da1947e49cb4625a166a4a2a%7C0%7C0%7
> > > C637625848601442706%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ
> > > IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=bOpIqV1g
> > > lMUXqz9rsX0UK3Oqap2J1cY86TGVOJvzYe4%3D&reserved=0
> > >
> > > Biju Das (18):
> > > dt-bindings: net: renesas,etheravb: Document Gigabit Ethernet IP
> > > drivers: clk: renesas: rzg2l-cpg: Add support to handle MUX clocks
> > > drivers: clk: renesas: r9a07g044-cpg: Add ethernet clock sources
> > > drivers: clk: renesas: r9a07g044-cpg: Add GbEthernet clock/reset
> >
> >
> > It's not a good idea to have the patch to the defferent subsystems
> > lumped all together in a single series...
>
> Agreed.
>
> Are these changes inseparable? If so, you need to be up front on this, and
> you need an agreement with the subsystem maintainers how the patches are
> going to be merged? Through which tree. And you need Acked-by from the
> other tree maintainers.
>
> Ideally you submit multiple patchsets. This assumes all sets will compile
> independently.
Agreed. Will split this patch series in 3 patchsets
1) single binding patch
2) Clock patchset
3) ravb driver patchset.
Cheers,
Biju
Powered by blists - more mailing lists