From: Shawn Guo <shawnguo@kernel.org>
To: "David S. Miller" <davem@davemloft.net>, Paolo Abeni <pabeni@redhat.com>
Cc: Clark Wang <xiaoning.wang@nxp.com>,
wei.fang@nxp.com, shenwei.wang@nxp.com, edumazet@google.com,
kuba@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, s.hauer@pengutronix.de,
festevam@gmail.com, peppe.cavallaro@st.com,
alexandre.torgue@foss.st.com, joabreu@synopsys.com,
mcoquelin.stm32@gmail.com, richardcochran@gmail.com,
linux-imx@nxp.com, kernel@pengutronix.de, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH V2 0/7] Add eqos and fec support for imx93
Date: Thu, 26 Jan 2023 09:02:16 +0800 [thread overview]
Message-ID: <20230126010214.GO20713@T480> (raw)
In-Reply-To: <6ee1798af93cc5b8c46611ecca941ee57481358e.camel@redhat.com>
On Tue, Jan 17, 2023 at 09:27:56AM +0100, Paolo Abeni wrote:
> Hi,
>
> On Fri, 2023-01-13 at 11:33 +0800, Clark Wang wrote:
> > This patchset add imx93 support for dwmac-imx glue driver.
> > There are some changes of GPR implement.
> > And add fec and eqos nodes for imx93 dts.
> >
> > Clark Wang (7):
> > net: stmmac: add imx93 platform support
> > dt-bindings: add mx93 description
> > dt-bindings: net: fec: add mx93 description
> > arm64: dts: imx93: add eqos support
> > arm64: dts: imx93: add FEC support
> > arm64: dts: imx93-11x11-evk: enable eqos
> > arm64: dts: imx93-11x11-evk: enable fec function
> >
> > .../devicetree/bindings/net/fsl,fec.yaml | 1 +
> > .../bindings/net/nxp,dwmac-imx.yaml | 4 +-
> > .../boot/dts/freescale/imx93-11x11-evk.dts | 78 +++++++++++++++++++
> > arch/arm64/boot/dts/freescale/imx93.dtsi | 48 ++++++++++++
> > .../net/ethernet/stmicro/stmmac/dwmac-imx.c | 55 +++++++++++--
> > 5 files changed, 180 insertions(+), 6 deletions(-)
>
> It's not clear to me if the whole series should go via netdev. I
> think/fear such option could cause later conflicts for Linus. Does it
> make sense to split this in 2 chunks, and have only the first 3 patches
> merged via netdev?
I share the same concern here.
David,
Could you *not* apply DTS patches in the future? People often include
driver changes and corresponding DTS ones in a single series to ease
cross reviewing and testing. If picking selected patches from a series
could a problem for your applying robot, we should probably start asking
people to split change-sets.
Shawn
next prev parent reply other threads:[~2023-01-26 1:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 3:33 [PATCH V2 0/7] Add eqos and fec support for imx93 Clark Wang
2023-01-13 3:33 ` [PATCH V2 1/7] net: stmmac: add imx93 platform support Clark Wang
2023-01-16 0:51 ` Peng Fan
2023-01-13 3:33 ` [PATCH V2 2/7] dt-bindings: add mx93 description Clark Wang
2023-01-13 3:33 ` [PATCH V2 3/7] dt-bindings: net: fec: " Clark Wang
2023-01-13 12:11 ` Krzysztof Kozlowski
2023-01-13 3:33 ` [PATCH V2 4/7] arm64: dts: imx93: add eqos support Clark Wang
2023-01-16 0:52 ` Peng Fan
2023-01-13 3:33 ` [PATCH V2 5/7] arm64: dts: imx93: add FEC support Clark Wang
2023-01-16 0:52 ` Peng Fan
2023-01-13 3:33 ` [PATCH V2 6/7] arm64: dts: imx93-11x11-evk: enable eqos Clark Wang
2023-01-16 0:52 ` Peng Fan
2023-01-13 3:33 ` [PATCH V2 7/7] arm64: dts: imx93-11x11-evk: enable fec function Clark Wang
2023-01-16 0:53 ` Peng Fan
2023-01-17 8:27 ` [PATCH V2 0/7] Add eqos and fec support for imx93 Paolo Abeni
2023-01-26 1:02 ` Shawn Guo [this message]
2023-01-18 13:10 ` 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=20230126010214.GO20713@T480 \
--to=shawnguo@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=festevam@gmail.com \
--cc=joabreu@synopsys.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shenwei.wang@nxp.com \
--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 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).