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: <20221010102914.ut364d57sjhnb3lj@skbuf> Date: Mon, 10 Oct 2022 13:29:14 +0300 From: Vladimir Oltean <olteanv@...il.com> To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> Cc: Jerry Ray <jerry.ray@...rochip.com>, Andrew Lunn <andrew@...n.ch>, Vivien Didelot <vivien.didelot@...il.com>, 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>, UNGLinuxDriver@...rochip.com, netdev@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [net-next][PATCH v4] dt-bindings: dsa: Add lan9303 yaml On Mon, Oct 10, 2022 at 06:23:24AM -0400, Krzysztof Kozlowski wrote: > 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: > >>>> > >>>> +MICROCHIP LAN9303/LAN9354 ETHERNET SWITCH DRIVER > >>>> +M: Jerry Ray <jerry.ray@...rochip.com> > >>>> +M: UNGLinuxDriver@...rochip.com > >>>> +L: netdev@...r.kernel.org > >>>> +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: > > https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git, or in > > other words, not net-next.git where new features are sent: > > https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git > > 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. Personally I'd split the patch into 2 pieces, the MAINTAINERS entry for the drivers/net/dsa/lan9303* portion, plus the current .txt schema, which goes to "net" right away, wait until the net tree gets merged back into net-next (happens when submissions for net-next reopen), then add the dt-bindings and rename the .txt schema from MAINTAINERS to .yaml.
Powered by blists - more mailing lists