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@xxxxxxxxxxxxx> > >>>> +M: UNGLinuxDriver@xxxxxxxxxxxxx > >>>> +L: netdev@xxxxxxxxxxxxxxx > >>>> +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.
