From: Geert Uytterhoeven <geert@linux-m68k.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Heiko Stuebner <heiko@sntech.de>
Subject: Re: [linux-next:master 968/1347] arch/arm64/boot/dts/rockchip/rk3399-eaidk-610.dtb: /i2c@ff110000/audio-codec@1a: failed to match any schema with compatible: ['realtek,rt5651']
Date: Tue, 1 Oct 2024 13:52:43 +0200 [thread overview]
Message-ID: <CAMuHMdUxFzMTpAb-4L5Q4vdUE4_mSRJxCMf-UoscDHuwH3-TUw@mail.gmail.com> (raw)
In-Reply-To: <202410011845.UiVJJtwf-lkp@intel.com>
On Tue, Oct 1, 2024 at 12:58 PM kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 77df9e4bb2224d8ffbddec04c333a9d7965dad6c
> commit: 2f39bba3b4f037d6c3c9174eed5befcef1c79abb [968/1347] arm64: dts: rockchip: Fix rt5651 compatible value on rk3399-eaidk-610
> config: arm64-randconfig-051-20241001 (https://download.01.org/0day-ci/archive/20241001/202410011845.UiVJJtwf-lkp@intel.com/config)
> compiler: aarch64-linux-gcc (GCC) 14.1.0
> dtschema version: 2024.10.dev4+g577c1ab
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241001/202410011845.UiVJJtwf-lkp@intel.com/reproduce)
> >> arch/arm64/boot/dts/rockchip/rk3399-eaidk-610.dtb: /i2c@ff110000/audio-codec@1a: failed to match any schema with compatible: ['realtek,rt5651']
This is expected, as Documentation/devicetree/bindings/sound/rt5651.txt
is still a plain text DT binding, and wasn't converted to json-schema yet.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2024-10-01 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 10:57 kernel test robot
2024-10-01 11:52 ` Geert Uytterhoeven [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=CAMuHMdUxFzMTpAb-4L5Q4vdUE4_mSRJxCMf-UoscDHuwH3-TUw@mail.gmail.com \
--to=geert@linux-m68k.org \
--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