From: Shawn Guo <shawnguo2@yeah.net>
To: Peng Fan <peng.fan@nxp.com>, kernel test robot <lkp@intel.com>
Cc: "oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: [shawnguo:imx/dt64 53/91] arch/arm64/boot/dts/freescale/imx95-19x19-evk.dtb: /: failed to match any schema with compatible: ['fsl,imx95-19x19-evk', 'fsl,imx95']
Date: Tue, 2 Jul 2024 14:50:38 +0800 [thread overview]
Message-ID: <ZoOjPtWSTTn8QryI@dragon> (raw)
In-Reply-To: <AM6PR04MB5941F075BB66E5D866A8F54988DC2@AM6PR04MB5941.eurprd04.prod.outlook.com>
On Tue, Jul 02, 2024 at 06:22:26AM +0000, Peng Fan wrote:
> > dtcheck warnings: (new ones prefixed by >>)
> > >> arch/arm64/boot/dts/freescale/imx95-19x19-evk.dtb: /: failed to
> > match
> > >> any schema with compatible: ['fsl,imx95-19x19-evk', 'fsl,imx95']
> > >> arch/arm64/boot/dts/freescale/imx95-19x19-evk.dtb: /: failed to
> > match
> > >> any schema with compatible: ['fsl,imx95-19x19-evk', 'fsl,imx95']
> > arch/arm64/boot/dts/freescale/imx95-19x19-evk.dtb: scmi:
> > protocol@19: Unevaluated properties are not allowed
> > ('regusdhc2vmmcgrp', 'uart1grp', 'usdhc1-100mhzgrp', 'usdhc1-
> > 200mhzgrp', 'usdhc1grp', 'usdhc2-100mhzgrp', 'usdhc2-200mhzgrp',
> > 'usdhc2gpiogrp', 'usdhc2grp' were unexpected)
>
> The binding is in Linus' pinctrl tree.
Hi lkp forks,
Thanks for all those reports! But could you stop such "make W=1 dtbs"
testing against my imx/dt64 (and imx/dt) branch but testing linux-next
instead? Binding changes may go via different trees.
Shawn
next prev parent reply other threads:[~2024-07-02 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202407021405.ahrmTsPb-lkp@intel.com>
2024-07-02 6:22 ` [shawnguo:imx/dt64 53/91] arch/arm64/boot/dts/freescale/imx95-19x19-evk.dtb: /: failed to match any schema with compatible: ['fsl,imx95-19x19-evk', 'fsl,imx95'] Peng Fan
2024-07-02 6:50 ` Shawn Guo [this message]
2024-07-02 8:39 ` Philip Li
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=ZoOjPtWSTTn8QryI@dragon \
--to=shawnguo2@yeah.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peng.fan@nxp.com \
--cc=shawnguo@kernel.org \
/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).