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, 10 Oct 2022 06:23:24 -0400
From:   Krzysztof Kozlowski <>
To:     Vladimir Oltean <>
Cc:     Jerry Ray <>, Andrew Lunn <>,
        Vivien Didelot <>,
        Florian Fainelli <>,
        "David S. Miller" <>,
        Eric Dumazet <>,
        Jakub Kicinski <>,
        Paolo Abeni <>,
        Rob Herring <>,
        Krzysztof Kozlowski <>,,,,
Subject: Re: [net-next][PATCH v4] dt-bindings: dsa: Add lan9303 yaml

On 09/10/2022 18:22, Vladimir Oltean wrote:
> On Sun, Oct 09, 2022 at 05:20:03PM +0200, Krzysztof Kozlowski wrote:
>> On 09/10/2022 00:56, Vladimir Oltean wrote:
>>>> +M:	Jerry Ray <>
>>>> +M:
>>>> +L:
>>>> +S:	Maintained
>>>> +F:	Documentation/devicetree/bindings/net/dsa/microchip,lan9303.yaml
>>>> +F:	drivers/net/dsa/lan9303*
>>>> +
>>> Separate patch please? Changes to the MAINTAINERS file get applied to
>>> the "net" tree.
>> This will also go via net tree, so there is no real need to split it.
> I meant exactly what I wrote, "net" tree as in the networking tree where
> fixes to the current master branch are sent:
>, or in
> other words, not net-next.git where new features are sent:

Ah, but how it can go to fixes? It has invalid path (in the context of
net-fixes) and it is not related to anything in the current cycle.

Best regards,

Powered by blists - more mailing lists