From: Paolo Abeni <pabeni@redhat.com>
To: Fabio Estevam <festevam@gmail.com>, shawnguo@kernel.org
Cc: wei.fang@nxp.com, shenwei.wang@nxp.com, xiaoning.wang@nxp.com,
kuba@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH 2/2] arm64: dts: imx8dxl-ss-conn: Complete the FEC compatibles
Date: Thu, 14 Sep 2023 08:16:42 +0200 [thread overview]
Message-ID: <eba4483dd75a1c18bdb24f7c41e701f96f1e2d0a.camel@redhat.com> (raw)
In-Reply-To: <9dd78edb2476cc5b57ce7f6b5c6bb338ebef43fd.camel@redhat.com>
On Tue, 2023-09-12 at 10:09 +0200, Paolo Abeni wrote:
> Hi,
>
> On Sat, 2023-09-09 at 09:31 -0300, Fabio Estevam wrote:
> > From: Fabio Estevam <festevam@denx.de>
> >
> > Use the full compatible list for the imx8dl FEC as per fsl,fec.yaml.
> >
> > This fixes the following schema warning:
> >
> > imx8dxl-evk.dtb: ethernet@5b040000: compatible: 'oneOf' conditional failed, one must be fixed:
> > ['fsl,imx8qm-fec'] is too short
> > 'fsl,imx8qm-fec' is not one of ['fsl,imx25-fec', 'fsl,imx27-fec', 'fsl,imx28-fec', 'fsl,imx6q-fec', 'fsl,mvf600-fec', 'fsl,s32v234-fec']
> > 'fsl,imx8qm-fec' is not one of ['fsl,imx53-fec', 'fsl,imx6sl-fec']
> > 'fsl,imx8qm-fec' is not one of ['fsl,imx35-fec', 'fsl,imx51-fec']
> > 'fsl,imx8qm-fec' is not one of ['fsl,imx6ul-fec', 'fsl,imx6sx-fec']
> > 'fsl,imx8qm-fec' is not one of ['fsl,imx7d-fec']
> > 'fsl,imx8mq-fec' was expected
> > 'fsl,imx8qm-fec' is not one of ['fsl,imx8mm-fec', 'fsl,imx8mn-fec', 'fsl,imx8mp-fec', 'fsl,imx93-fec']
> > 'fsl,imx8qm-fec' is not one of ['fsl,imx8dxl-fec', 'fsl,imx8qxp-fec']
> > 'fsl,imx8qm-fec' is not one of ['fsl,imx8ulp-fec']
> > from schema $id: http://devicetree.org/schemas/net/fsl,fec.yaml#
> >
> > Signed-off-by: Fabio Estevam <festevam@denx.de>
>
> It looks like this series is targeting the net-next tree, am I
> misreading this?
>
> I guess we could have small conflicts whatever target tree we will use,
> so I *think* the above should be ok. @Shawn Guo: do you prefer
> otherwise?
Thinking again about it, I assume this should go via the devicetree git
tree, so I'm dropping it from the netdev pw.
Please correct me otherwise, thanks!
Paolo
_______________________________________________
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:[~2023-09-14 6:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 12:31 [PATCH 1/2] dt-bindings: net: fec: Add imx8dxl description Fabio Estevam
2023-09-09 12:31 ` [PATCH 2/2] arm64: dts: imx8dxl-ss-conn: Complete the FEC compatibles Fabio Estevam
2023-09-12 8:09 ` Paolo Abeni
2023-09-14 6:16 ` Paolo Abeni [this message]
2023-09-14 10:27 ` Fabio Estevam
2023-09-25 2:02 ` Shawn Guo
2023-09-10 9:39 ` [PATCH 1/2] dt-bindings: net: fec: Add imx8dxl description Conor Dooley
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=eba4483dd75a1c18bdb24f7c41e701f96f1e2d0a.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--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).