From: kernel test robot <lkp@intel.com>
To: Marek Vasut <marex@denx.de>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Lunn <andrew@lunn.ch>
Subject: [linux-next:master 8728/10049] arch/arm64/boot/dts/renesas/r9a09g011-v2mevk2.dtb: ethernet-phy@0: compatible: ['ethernet-phy-id001c.c916', 'ethernet-phy-ieee802.3-c22'] is too long
Date: Wed, 3 Jul 2024 01:30:08 +0800 [thread overview]
Message-ID: <202407030109.R57yPLho-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 82e4255305c554b0bb18b7ccf2db86041b4c8b6e
commit: 8fda53719a596fa2a2880c42b5fa4126fbbbfc3d [8728/10049] dt-bindings: net: realtek,rtl82xx: Document known PHY IDs as compatible strings
config: arm64-randconfig-051-20240703 (https://download.01.org/0day-ci/archive/20240703/202407030109.R57yPLho-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
dtschema version: 2024.6.dev3+g650bf2d
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240703/202407030109.R57yPLho-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202407030109.R57yPLho-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
'renesas,rcar-gen2-sdhi' was expected
'renesas,rcar-gen4-sdhi' was expected
'renesas,rzg2l-sdhi' was expected
from schema $id: http://devicetree.org/schemas/mmc/renesas,sdhi.yaml#
arch/arm64/boot/dts/renesas/r9a09g011-v2mevk2.dtb: mmc@85020000: clocks: [[3, 1, 26], [3, 1, 28], [3, 1, 27], [3, 1, 25]] is too long
from schema $id: http://devicetree.org/schemas/mmc/renesas,sdhi.yaml#
arch/arm64/boot/dts/renesas/r9a09g011-v2mevk2.dtb: mmc@85020000: clock-names: ['core', 'clkh', 'cd', 'aclk'] is too long
from schema $id: http://devicetree.org/schemas/mmc/renesas,sdhi.yaml#
arch/arm64/boot/dts/renesas/r9a09g011-v2mevk2.dtb: mmc@85020000: Unevaluated properties are not allowed ('compatible' was unexpected)
from schema $id: http://devicetree.org/schemas/mmc/renesas,sdhi.yaml#
>> arch/arm64/boot/dts/renesas/r9a09g011-v2mevk2.dtb: ethernet-phy@0: compatible: ['ethernet-phy-id001c.c916', 'ethernet-phy-ieee802.3-c22'] is too long
from schema $id: http://devicetree.org/schemas/net/realtek,rtl82xx.yaml#
arch/arm64/boot/dts/renesas/r9a09g011-v2mevk2.dtb: pinctrl@b6250000: emmc: 'anyOf' conditional failed, one must be fixed:
'ctrl', 'data' do not match any of the regexes: 'pinctrl-[0-9]+'
'power-source' does not match any of the regexes: 'pinctrl-[0-9]+'
from schema $id: http://devicetree.org/schemas/pinctrl/renesas,rzv2m-pinctrl.yaml#
arch/arm64/boot/dts/renesas/r9a09g011-v2mevk2.dtb: pinctrl@b6250000: sd0: 'anyOf' conditional failed, one must be fixed:
'cd', 'ctrl', 'data' do not match any of the regexes: 'pinctrl-[0-9]+'
'power-source' does not match any of the regexes: 'pinctrl-[0-9]+'
from schema $id: http://devicetree.org/schemas/pinctrl/renesas,rzv2m-pinctrl.yaml#
arch/arm64/boot/dts/renesas/r9a09g011-v2mevk2.dtb: pinctrl@b6250000: sd0-uhs: 'anyOf' conditional failed, one must be fixed:
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-02 17:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202407030109.R57yPLho-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew@lunn.ch \
--cc=linux-mm@kvack.org \
--cc=marex@denx.de \
--cc=oe-kbuild-all@lists.linux.dev \
/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