All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Alistair Francis <alistair@alistair23.me>,
	kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [shawnguo:imx/dt 19/19] dtbs_check: arch/arm/boot/dts/imx7d-remarkable2.dt.yaml: /: compatible: 'oneOf' conditional failed, one must be fixed:
Date: Tue, 30 Mar 2021 16:22:50 +0800	[thread overview]
Message-ID: <20210330082250.GO22955@dragon> (raw)
In-Reply-To: <20210330010521.GM4176174@shao2-debian>

On Tue, Mar 30, 2021 at 09:05:21AM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git imx/dt
> head:   c11d56b3761c77f50368b4828cc5d9f5f343148d
> commit: c11d56b3761c77f50368b4828cc5d9f5f343148d [19/19] ARM: imx7d-remarkable2: Initial device tree for reMarkable2
> compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
> reproduce: make ARCH=arm dtbs_check
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>

Thanks for the report.  But this is a false alarm, because the bindings
update is on a different branch than imx/dt.

Shawn

> 
> 
> dtcheck warnings: (new ones prefixed by >>)
> >> arch/arm/boot/dts/imx7d-remarkable2.dt.yaml: /: compatible: 'oneOf' conditional failed, one must be fixed:
>    	['remarkable,imx7d-remarkable2', 'fsl,imx7d'] is too short
>    	['remarkable,imx7d-remarkable2', 'fsl,imx7d'] is too long
>    	Additional items are not allowed ('fsl,imx7d' was unexpected)
>    	'remarkable,imx7d-remarkable2' is not one of ['armadeus,imx1-apf9328', 'fsl,imx1ads']
>    	'remarkable,imx7d-remarkable2' is not one of ['fsl,imx23-evk', 'olimex,imx23-olinuxino']
>    	'remarkable,imx7d-remarkable2' is not one of ['fsl,imx25-pdk', 'karo,imx25-tx25']
>    	'remarkable,imx7d-remarkable2' is not one of ['eukrea,mbimxsd25-baseboard']
>    	'remarkable,imx7d-remarkable2' is not one of ['eukrea,mbimxsd25-baseboard-cmo-qvga', 'eukrea,mbimxsd25-baseboard-dvi-svga', 'eukrea,mbimxsd25-baseboard-dvi-vga']
>    	'remarkable,imx7d-remarkable2' is not one of ['armadeus,imx27-apf27', 'fsl,imx27-pdk']
>    	'armadeus,imx27-apf27dev' was expected
> 
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: [shawnguo:imx/dt 19/19] dtbs_check: arch/arm/boot/dts/imx7d-remarkable2.dt.yaml: /: compatible: 'oneOf' conditional failed, one must be fixed:
Date: Tue, 30 Mar 2021 16:22:50 +0800	[thread overview]
Message-ID: <20210330082250.GO22955@dragon> (raw)
In-Reply-To: <20210330010521.GM4176174@shao2-debian>

[-- Attachment #1: Type: text/plain, Size: 1826 bytes --]

On Tue, Mar 30, 2021 at 09:05:21AM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git imx/dt
> head:   c11d56b3761c77f50368b4828cc5d9f5f343148d
> commit: c11d56b3761c77f50368b4828cc5d9f5f343148d [19/19] ARM: imx7d-remarkable2: Initial device tree for reMarkable2
> compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
> reproduce: make ARCH=arm dtbs_check
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>

Thanks for the report.  But this is a false alarm, because the bindings
update is on a different branch than imx/dt.

Shawn

> 
> 
> dtcheck warnings: (new ones prefixed by >>)
> >> arch/arm/boot/dts/imx7d-remarkable2.dt.yaml: /: compatible: 'oneOf' conditional failed, one must be fixed:
>    	['remarkable,imx7d-remarkable2', 'fsl,imx7d'] is too short
>    	['remarkable,imx7d-remarkable2', 'fsl,imx7d'] is too long
>    	Additional items are not allowed ('fsl,imx7d' was unexpected)
>    	'remarkable,imx7d-remarkable2' is not one of ['armadeus,imx1-apf9328', 'fsl,imx1ads']
>    	'remarkable,imx7d-remarkable2' is not one of ['fsl,imx23-evk', 'olimex,imx23-olinuxino']
>    	'remarkable,imx7d-remarkable2' is not one of ['fsl,imx25-pdk', 'karo,imx25-tx25']
>    	'remarkable,imx7d-remarkable2' is not one of ['eukrea,mbimxsd25-baseboard']
>    	'remarkable,imx7d-remarkable2' is not one of ['eukrea,mbimxsd25-baseboard-cmo-qvga', 'eukrea,mbimxsd25-baseboard-dvi-svga', 'eukrea,mbimxsd25-baseboard-dvi-vga']
>    	'remarkable,imx7d-remarkable2' is not one of ['armadeus,imx27-apf27', 'fsl,imx27-pdk']
>    	'armadeus,imx27-apf27dev' was expected
> 
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  reply	other threads:[~2021-03-30  8:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30  1:05 [shawnguo:imx/dt 19/19] dtbs_check: arch/arm/boot/dts/imx7d-remarkable2.dt.yaml: /: compatible: 'oneOf' conditional failed, one must be fixed: kernel test robot
2021-03-30  1:05 ` kernel test robot
2021-03-30  8:22 ` Shawn Guo [this message]
2021-03-30  8:22   ` Shawn Guo
  -- strict thread matches above, loose matches on Subject: below --
2021-03-29 11:40 kernel test robot

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=20210330082250.GO22955@dragon \
    --to=shawnguo@kernel.org \
    --cc=alistair@alistair23.me \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=rong.a.chen@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.