devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Pandey, Radhey Shyam" <radhey.shyam.pandey@amd.com>,
	Paolo Abeni <pabeni@redhat.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>,
	"Katakam, Harini" <harini.katakam@amd.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@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
Date: Tue, 14 Jun 2022 15:57:50 -0700	[thread overview]
Message-ID: <25fe27c8-7048-28ee-8c5a-ac26ed080fca@linaro.org> (raw)
In-Reply-To: <1ae6dce1-0c5c-64f0-c6a4-b0f11a82f315@linaro.org>

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

  reply	other threads:[~2022-06-14 22:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 16:53 [PATCH v2 net-next] dt-bindings: net: xilinx: document xilinx emaclite driver binding Radhey Shyam Pandey
2022-06-14  9:09 ` Paolo Abeni
2022-06-14 21:09   ` Pandey, Radhey Shyam
2022-06-14 22:48     ` Krzysztof Kozlowski
2022-06-14 22:57       ` Krzysztof Kozlowski [this message]
2022-06-15  1:54       ` Jakub Kicinski
2022-06-16 17:46         ` Rob Herring
2022-06-15  8:30 ` patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=25fe27c8-7048-28ee-8c5a-ac26ed080fca@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=git@amd.com \
    --cc=harini.katakam@amd.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=radhey.shyam.pandey@amd.com \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).