Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 10 Oct 2022 13:29:14 +0300
From:   Vladimir Oltean <olteanv@gmail.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc:     Jerry Ray <jerry.ray@microchip.com>, Andrew Lunn <andrew@lunn.ch>,
        Vivien Didelot <vivien.didelot@gmail.com>,
        Florian Fainelli <f.fainelli@gmail.com>,
        "David S. Miller" <davem@davemloft.net>,
        Eric Dumazet <edumazet@google.com>,
        Jakub Kicinski <kuba@kernel.org>,
        Paolo Abeni <pabeni@redhat.com>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
        devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next][PATCH v4] dt-bindings: dsa: Add lan9303 yaml
Message-ID: <20221010102914.ut364d57sjhnb3lj@skbuf>
References: <20221003164624.4823-1-jerry.ray@microchip.com>
 <20221003164624.4823-1-jerry.ray@microchip.com>
 <20221008225628.pslsnwilrpvg3xdf@skbuf>
 <e49eb069-c66b-532c-0e8e-43575304187b@linaro.org>
 <20221009222257.f3fcl7mw3hdtp4p2@skbuf>
 <551ca020-d4bb-94bf-7091-755506d76f58@linaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <551ca020-d4bb-94bf-7091-755506d76f58@linaro.org>
Precedence: bulk

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@microchip.com>
> >>>> +M:	UNGLinuxDriver@microchip.com
> >>>> +L:	netdev@vger.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.