netdev - Re: [PATCH] dt-bindings: net: orion-mdio: Convert to JSON schema

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] [day] [month] [year] [list]

Message-ID: <20220507122949.2c929211@thinkpad>
Date:   Sat, 7 May 2022 12:29:49 +0200
From:   Marek Behún <kabel@...nel.org>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     Chris Packham <chris.packham@...iedtelesis.co.nz>,
        davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
        pabeni@...hat.com, robh+dt@...nel.org,
        krzysztof.kozlowski+dt@...aro.org, atenart@...nel.org,
        thomas.petazzoni@...e-electrons.com, f.fainelli@...il.com,
        netdev@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: net: orion-mdio: Convert to JSON schema

On Wed, 4 May 2022 23:35:59 +0200
Andrew Lunn <andrew@...n.ch> wrote:

> On Wed, May 04, 2022 at 04:36:02PM +1200, Chris Packham wrote:
> > Convert the marvell,orion-mdio binding to JSON schema.
> > 
> > Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>
> > ---
> > 
> > Notes:
> >     Thomas, Antione & Florian I hope you don't mind me putting you as
> >     maintainers of the binding. Between you you've written the majority of
> >     the mvmdio.c driver.  
> 
> I actually think it will be me doing any maintenance work on that
> driver.
> 
> >     This does throw up the following dtbs_check warnings for turris-mox:
> >     
> >     arch/arm64/boot/dts/marvell/armada-3720-turris-mox.dtb: mdio@...04: switch0@10:reg: [[16], [0]] is too long
> >             From schema: Documentation/devicetree/bindings/net/marvell,orion-mdio.yaml  
> 
> I assume this is coming from
> 
> 		reg = <0x10 0>;
> 
> This is odd. Lets see what Marek Behún has to say.

Looks like a mistake on my part.

Marek