[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220614185454.7479405c@kernel.org>
Date: Tue, 14 Jun 2022 18:54:54 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: "Pandey, Radhey Shyam" <radhey.shyam.pandey@....com>,
Paolo Abeni <pabeni@...hat.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"krzysztof.kozlowski+dt@...aro.org"
<krzysztof.kozlowski+dt@...aro.org>,
"Katakam, Harini" <harini.katakam@....com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"git (AMD-Xilinx)" <git@....com>
Subject: Re: [PATCH v2 net-next] dt-bindings: net: xilinx: document xilinx
emaclite driver binding
On Tue, 14 Jun 2022 15:48:43 -0700 Krzysztof Kozlowski wrote:
> > I have seen a mixed set of the convention for dts patches. They are following
> > both routes i.e device tree or subsystem repos provided acked from device
> > tree maintainer. If there is preference for device tree repo then I can drop
> > net-next from subject prefix and resend it for the dt repo.
>
> If you got Ack from Devicetree bindings maintainer (Rob Herring or me),
> then feel free to take it via net-next. I think, it is actually
> preferred, unless this is some fix which needs to go via DT (Rob's) tree.
>
> If you don't have these acks, then better don't take it :) unless it's
> really waiting too long on the lists. I hope it's not that case.
GTK, thanks. I'm also often confused by the correct tree for DT patches.
I'll revive the patch in PW and apply it later today.
Powered by blists - more mailing lists