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 16:29:43 +0000
From:   Vladimir Oltean <>
To:     Jakub Kicinski <>, Rob Herring <>
CC:     "" <>,
        "" <>,
        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 Mon, Aug 01, 2022 at 09:22:56AM -0700, Jakub Kicinski wrote:
> 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.)

I can post the v2 of this patch today with Rob's indications and the
correct indentation spotted by yamllint. I'm not going to fix the newly
introduced warnings in drivers' examples - I don't know how, for one thing,
that's hardware specific knowledge.

Rob, given that you've said DSA shouldn't validate the DT and then
reconsidered, I'd appreciate if you could leave some acks on patches 1
and 4 of that series, which deal with the kernel side of things, rather
than the dt-schema.

Powered by blists - more mailing lists