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  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]
Date:   Mon, 1 Aug 2022 09:22:56 -0700
From:   Jakub Kicinski <>
To:     Vladimir Oltean <>
        Rob Herring <>,
        Krzysztof Kozlowski <>,
        "David S. Miller" <>,
        Eric Dumazet <>,
        Paolo Abeni <>, Andrew Lunn <>,
        Vivien Didelot <>,
        Florian Fainelli <>,
        Oleksij Rempel <>,
        Christian Marangi <>,
        John Crispin <>,
        Kurt Kanzenbach <>,
        Mans Rullgard <>,
        Arun Ramadoss <>,
        Woojung Huh <>,,
        Claudiu Manoil <>,
        Alexandre Belloni <>,
        George McCollister <>,
        DENG Qingfang <>,
        Sean Wang <>,
        Landen Chao <>,
        Matthias Brugger <>,
        Hauke Mehrtens <>,
        Martin Blumenstingl <>,
        Aleksander Jan Bajkowski <>,
        Alvin Šipraga <>,
        Luiz Angelo Daros de Luca <>,
        Linus Walleij <>,
        Pawel Dembicki <>,
        Clément Léger <>,
        Geert Uytterhoeven <>,
        Russell King <>,
        Marek Behún <>,
        Marcin Wojtas <>
Subject: Re: [PATCH net-next] dt-bindings: net: dsa: make phylink bindings
 required for CPU/DSA ports

On Sun, 31 Jul 2022 18:00:06 +0300 Vladimir Oltean wrote:
> It is desirable that new DSA drivers are written to expect that all
> their ports register with phylink, and not rely on the DSA core's
> workarounds to skip this process.
> To that end, DSA is being changed to warn existing drivers when such DT
> blobs are in use:
> Introduce another layer of validation in the DSA DT schema, and assert
> that CPU and DSA ports must have phylink-related properties present.
> Suggested-by: Rob Herring <>
> Signed-off-by: Vladimir Oltean <>
> ---
> I've sent this patch separately because at least right now I don't have
> a reason to resend the other 4 patches linked above, and this has no
> dependency on those.

If I'm reading

correctly - the warnings are expected but there needs to be a change 
to properties, so CR? (FWIW I'd lean towards allowing it still, even
tho net-next got closed. Assuming v2 can get posted and acked today.)

Powered by blists - more mailing lists