From: Jakub Kicinski <kuba@kernel.org>
To: Camelia Alexandra Groza <camelia.groza@nxp.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Sean Anderson <sean.anderson@seco.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH net v2] powerpc: dts: t208x: Disable 10G on MAC1 and MAC2
Date: Thu, 22 Dec 2022 11:08:43 -0800 [thread overview]
Message-ID: <20221222110843.022b07b9@kernel.org> (raw)
In-Reply-To: <VI1PR04MB5807E65FA99FE10D53804445F2E89@VI1PR04MB5807.eurprd04.prod.outlook.com>
On Thu, 22 Dec 2022 15:41:00 +0000 Camelia Alexandra Groza wrote:
> > Reviewed-by: Camelia Groza <camelia.groza@nxp.com>
> > Tested-by: Camelia Groza <camelia.groza@nxp.com>
>
> I see the patch marked Not Applicable in the netdev patchwork.
> What tree will it go through?
I could be wrong but I think DTS patches are supposed to go via the
platform / arch trees. We mostly take bindings via the networking trees
(and DTS changes if they are part of a larger code+binding+dts set).
But we can obviously apply this patch if that's the preference of
the PowerPC maintainers..
next prev parent reply other threads:[~2022-12-22 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 17:29 [PATCH net v2] powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 Sean Anderson
2022-12-19 16:23 ` Camelia Alexandra Groza
2022-12-22 15:41 ` Camelia Alexandra Groza
2022-12-22 19:08 ` Jakub Kicinski [this message]
2022-12-22 23:30 ` Michael Ellerman
2022-12-23 1:56 ` Jakub Kicinski
2022-12-23 2:00 ` 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=20221222110843.022b07b9@kernel.org \
--to=kuba@kernel.org \
--cc=camelia.groza@nxp.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.anderson@seco.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).