[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <be37815e-f47b-4f26-9921-38cae0d4b545@lunn.ch>
Date: Tue, 12 Mar 2024 23:09:04 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Niklas Söderlund <niklas.soderlund+renesas@...natech.se>
Cc: Sergey Shtylyov <s.shtylyov@....ru>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Geert Uytterhoeven <geert+renesas@...der.be>,
netdev@...r.kernel.org, devicetree@...r.kernel.org,
linux-renesas-soc@...r.kernel.org
Subject: Re: [net-next] dt-bindings: net: renesas,ethertsn: Create child-node
for MDIO bus
On Mon, Mar 11, 2024 at 03:35:07PM +0100, Niklas Söderlund wrote:
> The design for this driver followed that of other Renesas Ethernet
> drivers and thus did not force a child-node for the MDIO bus. As there
> are no upstream drivers or users of this binding yet take the
> opportunity to correct this and force the usage of a child-node for the
> MDIO bus.
Could you expand on the history. When was renesas,ethertsn.yaml added
and via which tree? Is this currently only in net-next and just sent
to Linus as part of this merge window? Or has it been around longer?
Andrew
Powered by blists - more mailing lists