linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Alex Bee <knaerzche@gmail.com>, 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 1912/4582] dtbs_check: arch/arm/boot/dts/rockchip/rk3128-evb.dtb: /dsi@10110000: failed to match any schema with compatible: ['rockchip,rk3128-mipi-dsi', 'snps,dw-mipi-dsi']
Date: Sat, 08 Jun 2024 13:26:16 +0200	[thread overview]
Message-ID: <3048353.WAvfycf1tz@diego> (raw)
In-Reply-To: <202406081302.0CAdvAA9-lkp@intel.com>

Am Samstag, 8. Juni 2024, 07:58:10 CEST schrieb kernel test robot:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   d35b2284e966c0bef3e2182a5c5ea02177dd32e4
> commit: 73fc389129dfe22b5706b4b6cbc1a4f86d1fbc1b [1912/4582] ARM: dts: rockchip: Add DSI for RK3128
> compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
> dtschema version: 2024.6.dev1+g833054f
> reproduce: (https://download.01.org/0day-ci/archive/20240608/202406081302.0CAdvAA9-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/202406081302.0CAdvAA9-lkp@intel.com/
> 
> dtcheck warnings: (new ones prefixed by >>)
> >> arch/arm/boot/dts/rockchip/rk3128-evb.dtb: /dsi@10110000: failed to match any schema with compatible: ['rockchip,rk3128-mipi-dsi', 'snps,dw-mipi-dsi']
> --
> >> arch/arm/boot/dts/rockchip/rk3128-xpi-3128.dtb: /dsi@10110000: failed to match any schema with compatible: ['rockchip,rk3128-mipi-dsi', 'snps,dw-mipi-dsi']

I guess something went wrong when that specific next-tree was constructed.
Looking at the current linux-next, the drm-specific parts really are not
present, but they are in the drm-misc tree for a while now:

https://cgit.freedesktop.org/drm/drm-misc/commit/?id=9bb3d9ad3e19f16efc34f427a58e480424c56a16
(in the correct drm-misc-next branch) and has been in a pull request
to main drm on may 30th [0]

Not sure if Dave is on vacation or so.


[0] https://patchwork.kernel.org/project/intel-gfx/patch/20240530-hilarious-flat-magpie-5fa186@houat/




  reply	other threads:[~2024-06-08 11:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-08  5:58 kernel test robot
2024-06-08 11:26 ` Heiko Stübner [this message]
2024-06-08 11:48   ` Alex Bee

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=3048353.WAvfycf1tz@diego \
    --to=heiko@sntech.de \
    --cc=knaerzche@gmail.com \
    --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