netdev - Re: [PATCH] dt-bindings: net: mdio: use non vendor specific compatible string in example

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: <60f445a1-e401-afeb-6b8f-4a16b92b43c8@gmail.com>
Date:   Thu, 5 Dec 2019 09:29:07 -0800
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Simon Horman <simon.horman@...ronome.com>,
        Grygorii Strashko <grygorii.strashko@...com>
Cc:     "David S. Miller" <davem@...emloft.net>,
        Andrew Lunn <andrew@...n.ch>,
        Heiner Kallweit <hkallweit1@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        devicetree@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: net: mdio: use non vendor specific
 compatible string in example

On 12/5/19 6:48 AM, Simon Horman wrote:
> On Wed, Nov 27, 2019 at 05:39:28PM +0200, Grygorii Strashko wrote:
>> Use non vendor specific compatible string in example, otherwise DT YAML
>> schemas validation may trigger warnings specific to TI ti,davinci_mdio
>> and not to the generic MDIO example.
>>
>> Signed-off-by: Grygorii Strashko <grygorii.strashko@...com>
> 
> This seems sensible to me.
> 
> Reviewed-by: Simon Horman <simon.horman@...ronome.com>
> 
> Are there any plans to address the errors DT YAML schema validation reports?

Sure, let me try to tackle this weekend.

> 
> $ ARCH=arm make dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/net/mdio.yaml
> .../linux/arch/arm/boot/dts/bcm4708-asus-rt-ac56u.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4708-asus-rt-ac56u.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4708-netgear-r6250.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4708-netgear-r6250.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4708-linksys-ea6300-v1.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4708-linksys-ea6300-v1.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4708-asus-rt-ac68u.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4708-asus-rt-ac68u.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4708-linksys-ea6500-v2.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4708-linksys-ea6500-v2.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4708-buffalo-wzr-1750dhp.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4708-buffalo-wzr-1750dhp.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4708-luxul-xap-1510.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4708-luxul-xap-1510.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47081-luxul-xwr-1200.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47081-luxul-xwr-1200.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47081-buffalo-wzr-600dhp2.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47081-buffalo-wzr-600dhp2.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4708-smartrg-sr400ac.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4708-smartrg-sr400ac.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4708-luxul-xwc-1000.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4708-luxul-xwc-1000.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4708-netgear-r6300-v2.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4708-netgear-r6300-v2.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47081-asus-rt-n18u.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47081-asus-rt-n18u.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4709-asus-rt-ac87u.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4709-asus-rt-ac87u.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47081-tplink-archer-c5-v2.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47081-tplink-archer-c5-v2.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47081-buffalo-wzr-900dhp.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47081-buffalo-wzr-900dhp.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4709-netgear-r7000.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4709-netgear-r7000.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4709-linksys-ea9200.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4709-linksys-ea9200.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47081-luxul-xap-1410.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47081-luxul-xap-1410.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47094-luxul-xwr-3150-v1.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47094-luxul-xwr-3150-v1.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47094-luxul-xap-1610.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47094-luxul-xap-1610.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47094-dlink-dir-885l.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47094-dlink-dir-885l.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4709-netgear-r8000.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4709-netgear-r8000.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4709-buffalo-wxr-1900dhp.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4709-buffalo-wxr-1900dhp.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm4709-tplink-archer-c9-v1.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm4709-tplink-archer-c9-v1.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47094-luxul-abr-4500.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47094-luxul-abr-4500.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47094-linksys-panamera.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47094-linksys-panamera.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47094-luxul-xwr-3100.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47094-luxul-xwr-3100.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm94709.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm94709.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47094-luxul-xbr-4500.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47094-luxul-xbr-4500.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47094-phicomm-k3.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47094-phicomm-k3.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm911360k.dt.yaml: mdio@...02000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm911360k.dt.yaml: mdio@...02000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm47094-netgear-r8500.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm47094-netgear-r8500.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm94708.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm94708.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm953012k.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm953012k.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm953012er.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm953012er.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm911360_entphn.dt.yaml: mdio@...02000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm911360_entphn.dt.yaml: mdio@...02000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm953012hr.dt.yaml: mdio@...03000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm953012hr.dt.yaml: mdio@...03000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm958305k.dt.yaml: mdio@...02000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm958305k.dt.yaml: mdio@...02000: #size-cells:0:0: 0 was expected
> .../linux/arch/arm/boot/dts/bcm958300k.dt.yaml: mdio@...02000: #address-cells:0:0: 1 was expected
> .../linux/arch/arm/boot/dts/bcm958300k.dt.yaml: mdio@...02000: #size-cells:0:0: 0 was expected
> 


-- 
Florian