netdev - Re: [RFC net-next 1/2] dt-bindings: ethernet-controller: create a type for PHY interface modes

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: <YFkH6AKEAaPbhy9f@lunn.ch>
Date:   Mon, 22 Mar 2021 22:11:04 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Marek Behún <kabel@...nel.org>
Cc:     netdev@...r.kernel.org, "David S . Miller" <davem@...emloft.net>,
        Florian Fainelli <f.fainelli@...il.com>,
        Heiner Kallweit <hkallweit1@...il.com>,
        Russell King <rmk+kernel@...linux.org.uk>,
        Rob Herring <robh@...nel.org>, devicetree@...r.kernel.org
Subject: Re: [RFC net-next 1/2] dt-bindings: ethernet-controller: create a
 type for PHY interface modes

On Mon, Mar 22, 2021 at 08:49:58PM +0100, Marek Behún wrote:
> In order to be able to define a property describing an array of PHY
> interface modes, we need to change the current scalar
> `phy-connection-type`, which lists the possible PHY interface modes, to
> an array of length 1 (otherwise we would need to define the same list at
> two different places).

Hi Marek

Please could you include a 0/2 patch which explains the big
picture. It is not clear to me why you need these properties.  What is
the problem you are trying to solve? That should be in the patch
series cover note.

	 Andrew