netdev - Re: [net-next,v4 0/2] ravb: Support describing the MDIO bus

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240328094546.GI1108818@ragnatech.se>
Date: Thu, 28 Mar 2024 10:45:46 +0100
From: Niklas Söderlund <niklas.soderlund+renesas@...natech.se>
To: 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+dt@...nel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Geert Uytterhoeven <geert+renesas@...der.be>,
	Claudiu Beznea <claudiu.beznea.uj@...renesas.com>,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
	Biju Das <biju.das.jz@...renesas.com>, netdev@...r.kernel.org,
	devicetree@...r.kernel.org
Cc: linux-renesas-soc@...r.kernel.org
Subject: Re: [net-next,v4 0/2] ravb: Support describing the MDIO bus

Hi netdev,

This series was marked as Deferred in patchwork. I just wonder why that 
is? Patch 1/2 touches bindings so it could go thru the Renesas tree but 
patch 2/2 touches the driver and depends on 1/2. Should not this whole 
series go thru net-next?

I fear it might have been flagged as Deferred as v3 was posted on the 
same day net-next closed and was therefore closed as Deferred.

On 2024-03-25 16:34:49 +0100, Niklas Söderlund wrote:
> Hello,
> 
> This series adds support to the binding and driver of the Renesas
> Ethernet AVB to described the MDIO bus. Currently the driver uses the OF
> node of the device itself when registering the MDIO bus. This forces any
> MDIO bus properties the MDIO core should react on to be set on the
> device OF node. This is confusing and non of the MDIO bus properties are
> described in the Ethernet AVB bindings.
> 
> Patch 1/2 extends the bindings with an optional mdio child-node to the
> device that can be used to contain the MDIO bus settings. While patch
> 2/2 changes the driver to use this node (if present) when registering
> the MDIO bus.
> 
> If the new optional mdio child-node is not present the driver fallback
> to the old behavior and uses the device OF node like before. This change
> is fully backward compatible with existing usage of the bindings.
> 
> For changelog see individual patches.
> 
> Niklas Söderlund (2):
>   dt-bindings: net: renesas,etheravb: Add optional MDIO bus node
>   ravb: Add support for an optional MDIO mode
> 
>  .../devicetree/bindings/net/renesas,etheravb.yaml    | 12 ++++++++++--
>  drivers/net/ethernet/renesas/ravb_main.c             |  9 ++++++++-
>  2 files changed, 18 insertions(+), 3 deletions(-)
> 
> -- 
> 2.44.0
> 

-- 
Kind Regards,
Niklas Söderlund