devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	"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>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>,
	"Katakam, Harini" <harini.katakam@amd.com>,
	"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: Thu, 16 Jun 2022 11:46:42 -0600	[thread overview]
Message-ID: <CAL_Jsq+32b6GcoX4+d7bnu512-FFaFgb3AEn=iEM_54Mp59RHQ@mail.gmail.com> (raw)
In-Reply-To: <20220614185454.7479405c@kernel.org>

On Tue, Jun 14, 2022 at 7:54 PM Jakub Kicinski <kuba@kernel.org> wrote:
>
> 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.

It is documented in
Documentation/devicetree/bindings/submitting-patches.rst, section II.

The default is bindings should go thru subsystem trees. Given netdev's
tendency to apply bindings before DT review and even semi-automated
checks, but skipping standalone patches, I haven't minded picking them
up.

Rob

  reply	other threads:[~2022-06-16 17:47 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
2022-06-15  1:54       ` Jakub Kicinski
2022-06-16 17:46         ` Rob Herring [this message]
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='CAL_Jsq+32b6GcoX4+d7bnu512-FFaFgb3AEn=iEM_54Mp59RHQ@mail.gmail.com' \
    --to=robh+dt@kernel.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=krzysztof.kozlowski@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 \
    /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).