From: Alex Bee <knaerzche@gmail.com>
To: "Heiko Stübner" <heiko@sntech.de>, "kernel test robot" <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 7406/9027] arch/arm64/boot/dts/rockchip/rk3368-lba3368.dtb: /i2c@ff660000/codec@1c: failed to match any schema with compatible: ['realtek,rt5640']
Date: Fri, 28 Jun 2024 14:31:38 +0200 [thread overview]
Message-ID: <934e3569-fae5-4ad2-ad36-419201fa970a@gmail.com> (raw)
In-Reply-To: <2736121.mvXUDI8C0e@diego>
Am 28.06.24 um 13:48 schrieb Heiko Stübner:
> Am Freitag, 28. Juni 2024, 02:55:26 CEST schrieb kernel test robot:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> head: 642a16ca7994a50d7de85715996a8ce171a5bdfb
>> commit: 7b4a8097e58b608638d416bd57469f8a9ab70e7b [7406/9027] arm64: dts: rockchip: Add Neardi LBA3368 board
>> config: arm64-randconfig-051-20240628 (https://download.01.org/0day-ci/archive/20240628/202406280804.Kc8B4xzn-lkp@intel.com/config)
>> compiler: aarch64-linux-gcc (GCC) 13.2.0
>> dtschema version: 2024.6.dev2+g3b69bad
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240628/202406280804.Kc8B4xzn-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/202406280804.Kc8B4xzn-lkp@intel.com/
>>
>> dtcheck warnings: (new ones prefixed by >>)
>>>> arch/arm64/boot/dts/rockchip/rk3368-lba3368.dtb: /i2c@ff660000/codec@1c: failed to match any schema with compatible: ['realtek,rt5640']
>>>> arch/arm64/boot/dts/rockchip/rk3368-lba3368.dtb: /mbox@ff6b0000: failed to match any schema with compatible: ['rockchip,rk3368-mailbox']
>> arch/arm64/boot/dts/rockchip/rk3368-lba3368.dtb: i2s-8ch@ff898000: '#sound-dai-cells' is a required property
>> from schema $id: http://devicetree.org/schemas/sound/rockchip-i2s.yaml#
>>
>>
> The sound-dai-cells are fixed already by
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=8d7ec44aa5d1eb94a30319074762a1740440cdc8
> ("arm64: dts: rockchip: Add sound-dai-cells for RK3368")
>
> and the other two stem from those bindings not being converted
> to yaml yet.
Yeah, ....
Looking at
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/arch/arm64/boot/dts/rockchip
the commits are in the "correct" order ... not sure what's wrong here. It
was pretty much the same with the CLK_NR_CLKS removal recently. It looks
like the kernel test robot builds every single commit (which is fine), but
the order it applies the patches seems to differ from git log.
>
prev parent reply other threads:[~2024-06-28 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 0:55 [linux-next:master 7406/9027] arch/arm64/boot/dts/rockchip/rk3368-lba3368.dtb: /i2c@ff660000/codec@1c: failed to match any schema with compatible: ['realtek,rt5640'] kernel test robot
2024-06-28 11:48 ` Heiko Stübner
2024-06-28 12:31 ` Alex Bee [this message]
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=934e3569-fae5-4ad2-ad36-419201fa970a@gmail.com \
--to=knaerzche@gmail.com \
--cc=heiko@sntech.de \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).