From: Niklas Cassel <cassel@kernel.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [linux-next:master 8329/9027] arch/arm64/boot/dts/rockchip/rk3588-armsom-sige7.dtb: /pcie-ep@fe150000: failed to match any schema with compatible: ['rockchip,rk3588-pcie-ep']
Date: Fri, 28 Jun 2024 16:51:04 +0200 [thread overview]
Message-ID: <Zn7N2Ak3_72qbJyo@ryzen.lan> (raw)
In-Reply-To: <4126102.zXnORWrf4K@diego>
On Fri, Jun 28, 2024 at 01:27:35AM +0200, Heiko Stübner wrote:
> Hi,
>
> Am Freitag, 28. Juni 2024, 01:16:09 CEST schrieb kernel test robot:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 642a16ca7994a50d7de85715996a8ce171a5bdfb
> > commit: 2fe9fe4e54f5763b8b681478dda9ac61fd42ecaf [8329/9027] arm64: dts: rockchip: Add PCIe endpoint mode support
> > config: arm64-randconfig-051-20240628 (https://download.01.org/0day-ci/archive/20240628/202406280710.UM3PNqsz-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/202406280710.UM3PNqsz-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/202406280710.UM3PNqsz-lkp@intel.com/
> >
> > dtcheck warnings: (new ones prefixed by >>)
> > >> arch/arm64/boot/dts/rockchip/rk3588-armsom-sige7.dtb: /pcie-ep@fe150000: failed to match any schema with compatible: ['rockchip,rk3588-pcie-ep']
>
> the compatible is part of the binding that was applied to the pci
> tree in [0], so this should resolve itself in next shortly, I hope.
I think so too.
The pci/next branch hasn't been updated for 9 days:
commit f117d19a8dc6e765092d674d36c5cbc2cc00102c (pci/next)
Merge: d745ced0b5fa 3dadb4871578
Author: Bjorn Helgaas <bhelgaas@google.com>
Date: Wed Jun 19 13:44:38 2024 -0500
even though the topic branches have queued up newer stuff (including the
dt-bindings), so hopefully they will update their for-next branch soon.
Kind regards,
Niklas
prev parent reply other threads:[~2024-06-28 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 23:16 kernel test robot
2024-06-27 23:27 ` Heiko Stübner
2024-06-28 14:51 ` Niklas Cassel [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=Zn7N2Ak3_72qbJyo@ryzen.lan \
--to=cassel@kernel.org \
--cc=heiko@sntech.de \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=manivannan.sadhasivam@linaro.org \
--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