Messages in this thread | | | Date | Tue, 14 Jun 2022 15:57:50 -0700 | Subject | Re: [PATCH v2 net-next] dt-bindings: net: xilinx: document xilinx emaclite driver binding | From | Krzysztof Kozlowski <> |
| |
On 14/06/2022 15:48, Krzysztof Kozlowski wrote: > On 14/06/2022 14:09, Pandey, Radhey Shyam wrote: >> [AMD Official Use Only - General] >> >>> -----Original Message----- >>> From: Paolo Abeni <pabeni@redhat.com> >>> Sent: Tuesday, June 14, 2022 2:40 PM >>> To: Pandey, Radhey Shyam <radhey.shyam.pandey@amd.com>; >>> davem@davemloft.net; edumazet@google.com; kuba@kernel.org; >>> robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org; Katakam, Harini >>> <harini.katakam@amd.com> >>> Cc: netdev@vger.kernel.org; devicetree@vger.kernel.org; linux- >>> kernel@vger.kernel.org; git (AMD-Xilinx) <git@amd.com> >>> Subject: Re: [PATCH v2 net-next] dt-bindings: net: xilinx: document xilinx >>> emaclite driver binding >>> >>> On Thu, 2022-06-09 at 22:23 +0530, Radhey Shyam Pandey wrote: >>>> Add basic description for the xilinx emaclite driver DT bindings. >>>> >>>> Signed-off-by: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com> >>> >>> Even if marked for 'net-next', my understanding is that should go via the >>> device tree repo. I'm dropping from the netdev patchwork, please correct me if >>> I'm wrong, thanks! >> >> 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.
I got this reply in my mailbox but I cannot find at all the original patch, which might explain why it was not acked. I found it on lore, though. Rob had here questions but I think you resolved/answered them, so from my side:
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards, Krzysztof
| |