linux-kernel - Re: [PATCH v2 5/5] ARM: dts: NSP: Fix MX65 MDIO mux warnings

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]

Date:   Thu,  2 Sep 2021 14:06:06 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     bcm-kernel-feedback-list@...adcom.com,
        Matthew Hagan <mnhagan88@...il.com>
Cc:     Andrew Lunn <andrew@...n.ch>, Rob Herring <robh+dt@...nel.org>,
        Ray Jui <rjui@...adcom.com>,
        Scott Branden <sbranden@...adcom.com>,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 5/5] ARM: dts: NSP: Fix MX65 MDIO mux warnings

On Sun, 29 Aug 2021 22:37:51 +0000, Matthew Hagan <mnhagan88@...il.com> wrote:
> The naming of this node is based upon that of the initial EA9500 dts[1].
> However this does not conform with the mdio-mux format, yielding the
> following message when running dtbs_check:
> mdio-mii-mux: $nodename:0: 'mdio-mii-mux' does not match '^mdio-mux[\\-@]?'
> 
> Secondly, this node should be moved to within the axi node and given the
> appropriate unit address. This also requires exposing the axi node via a
> label in bcm-nsp.dtsi. This fixes the following warning:
> Warning (unit_address_vs_reg): /mdio-mii-mux: node has a reg or ranges property, but no unit name
> 
> [1]https://patchwork.ozlabs.org/project/linux-imx/patch/20180618174159.86150-1-npcomplete13@gmail.com/#1941353
> 
> Signed-off-by: Matthew Hagan <mnhagan88@...il.com>
> ---

Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
--
Florian