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
| ||
|
Message-ID: <58b87aea-c7f5-4e7d-9736-74a2ed997306@arinc9.com> Date: Wed, 13 Sep 2023 17:36:36 +0300 From: Arınç ÜNAL <arinc.unal@...nc9.com> To: Vladimir Oltean <olteanv@...il.com> Cc: Andrew Lunn <andrew@...n.ch>, Florian Fainelli <f.fainelli@...il.com>, "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>, Woojung Huh <woojung.huh@...rochip.com>, UNGLinuxDriver@...rochip.com, Linus Walleij <linus.walleij@...aro.org>, Alvin Šipraga <alsi@...g-olufsen.dk>, Daniel Golle <daniel@...rotopia.org>, Landen Chao <Landen.Chao@...iatek.com>, DENG Qingfang <dqfext@...il.com>, Sean Wang <sean.wang@...iatek.com>, Matthias Brugger <matthias.bgg@...il.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>, mithat.guner@...ont.com, erkin.bozoglu@...ont.com, netdev@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org Subject: Re: [PATCH 2/4] dt-bindings: net: dsa: document internal MDIO bus On 13.09.2023 16:00, Vladimir Oltean wrote: > On Wed, Sep 13, 2023 at 02:35:11PM +0300, Arınç ÜNAL wrote: >> On 13.09.2023 14:04, Vladimir Oltean wrote: >>> I don't think they're for switch ports only. Any driver which uses >>> phylink_fwnode_phy_connect() or its derivatives gets subject to the same >>> bindings. But putting the sub-schema in ethernet-controller.yaml makes >>> sense, just maybe not naming it "phylink-switch". >> >> Got it. Should we disallow managed altogether when fixed-link is also >> defined, or just with in-band-status value? > > Just with the "in-band-status" value - just like phylink_parse_mode() > implies. If not possible, just leave that condition out. I can rewrite the property to allow values other than in-band-status. - if: required: [ fixed-link ] then: properties: managed: const: auto Arınç
Powered by blists - more mailing lists