From: Jakub Kicinski <kuba@kernel.org>
To: Shawn Guo <shawnguo2@yeah.net>
Cc: Frank Li <Frank.Li@nxp.com>, Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>, Wei Fang <wei.fang@nxp.com>,
Shenwei Wang <shenwei.wang@nxp.com>,
Clark Wang <xiaoning.wang@nxp.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH v2 0/4] Add 8qm SMMU information
Date: Tue, 6 Feb 2024 07:41:51 -0800 [thread overview]
Message-ID: <20240206074151.577d33f1@kernel.org> (raw)
In-Reply-To: <ZcIPCxgO3Gxc/aXh@dragon>
On Tue, 6 Feb 2024 18:50:51 +0800 Shawn Guo wrote:
> > Any preference on whether all these go via a platform tree,
> > or should we pick up the net patch to netdev? I guess taking
> > the DTB via netdev would be the usual way to handle this?
>
> No, it's not. Taking DTS changes through arch/platform tree is the
> usual way.
I said DTB.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Shawn Guo <shawnguo2@yeah.net>
Cc: Frank Li <Frank.Li@nxp.com>, Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>, Wei Fang <wei.fang@nxp.com>,
Shenwei Wang <shenwei.wang@nxp.com>,
Clark Wang <xiaoning.wang@nxp.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH v2 0/4] Add 8qm SMMU information
Date: Tue, 6 Feb 2024 07:41:51 -0800 [thread overview]
Message-ID: <20240206074151.577d33f1@kernel.org> (raw)
In-Reply-To: <ZcIPCxgO3Gxc/aXh@dragon>
On Tue, 6 Feb 2024 18:50:51 +0800 Shawn Guo wrote:
> > Any preference on whether all these go via a platform tree,
> > or should we pick up the net patch to netdev? I guess taking
> > the DTB via netdev would be the usual way to handle this?
>
> No, it's not. Taking DTS changes through arch/platform tree is the
> usual way.
I said DTB.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-06 15:41 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 20:22 [PATCH v2 0/4] Add 8qm SMMU information Frank Li
2024-02-01 20:22 ` Frank Li
2024-02-01 20:22 ` [PATCH v2 1/4] dt-bindings: mmc: fsl-imx-esdhc: add iommus property Frank Li
2024-02-01 20:22 ` Frank Li
2024-02-02 8:23 ` Krzysztof Kozlowski
2024-02-02 8:23 ` Krzysztof Kozlowski
2024-02-05 17:28 ` Ulf Hansson
2024-02-05 17:28 ` Ulf Hansson
2024-02-01 20:22 ` [PATCH v2 2/4] dt-bindings: net: fec: " Frank Li
2024-02-01 20:22 ` Frank Li
2024-02-02 8:23 ` Krzysztof Kozlowski
2024-02-02 8:23 ` Krzysztof Kozlowski
2024-02-16 19:22 ` Frank Li
2024-02-16 19:22 ` Frank Li
2024-02-17 8:18 ` Krzysztof Kozlowski
2024-02-17 8:18 ` Krzysztof Kozlowski
2024-02-19 19:44 ` Jakub Kicinski
2024-02-19 19:44 ` Jakub Kicinski
2024-02-01 20:22 ` [PATCH v2 3/4] arm64: dts: imx8qm: add smmu node Frank Li
2024-02-01 20:22 ` Frank Li
2024-02-06 10:52 ` Shawn Guo
2024-02-06 10:52 ` Shawn Guo
2024-02-01 20:22 ` [PATCH v2 4/4] arm64: dts: imx8qm: add smmu stream id information Frank Li
2024-02-01 20:22 ` Frank Li
2024-02-06 10:53 ` Shawn Guo
2024-02-06 10:53 ` Shawn Guo
2024-02-02 19:05 ` [PATCH v2 0/4] Add 8qm SMMU information Jakub Kicinski
2024-02-02 19:05 ` Jakub Kicinski
2024-02-02 22:28 ` Frank Li
2024-02-02 22:28 ` Frank Li
2024-02-05 9:25 ` Krzysztof Kozlowski
2024-02-05 9:25 ` Krzysztof Kozlowski
2024-02-05 19:55 ` Frank Li
2024-02-05 19:55 ` Frank Li
2024-02-06 10:50 ` Shawn Guo
2024-02-06 10:50 ` Shawn Guo
2024-02-06 15:41 ` Jakub Kicinski [this message]
2024-02-06 15:41 ` Jakub Kicinski
2024-02-23 2:07 ` Shawn Guo
2024-02-23 2:07 ` Shawn Guo
2024-02-23 2:26 ` Jakub Kicinski
2024-02-23 2:26 ` Jakub Kicinski
2024-02-19 19:50 ` patchwork-bot+netdevbpf
2024-02-19 19:50 ` 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=20240206074151.577d33f1@kernel.org \
--to=kuba@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo2@yeah.net \
--cc=shawnguo@kernel.org \
--cc=shenwei.wang@nxp.com \
--cc=ulf.hansson@linaro.org \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.