From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH 1/1] ARM: dts: rockchip: Wifi improvements for Sonoff iHost
Date: Wed, 30 Apr 2025 08:23:31 +0800 [thread overview]
Message-ID: <202504300816.UPjewbSf-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "dtcheck: binding changes may go via different trees"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20250427065013.99871-2-hao.zhang@coolkit.cn>
References: <20250427065013.99871-2-hao.zhang@coolkit.cn>
TO: Hao Zhang <hao.zhang@coolkit.cn>
TO: linux-rockchip@lists.infradead.org
CC: devicetree@vger.kernel.org
CC: linux-arm-kernel@lists.infradead.org
CC: conor+dt@kernel.org
CC: heiko@sntech.de
CC: krzysztof.kozlowski+dt@linaro.org
CC: robh+dt@kernel.org
CC: linux-kernel@vger.kernel.org
CC: "hao.zhang" <hao.zhang@coolkit.cn>
Hi Hao,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rockchip/for-next]
[also build test WARNING on linus/master v6.15-rc4 next-20250429]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Hao-Zhang/ARM-dts-rockchip-Wifi-improvements-for-Sonoff-iHost/20250427-155046
base: https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git for-next
patch link: https://lore.kernel.org/r/20250427065013.99871-2-hao.zhang%40coolkit.cn
patch subject: [PATCH 1/1] ARM: dts: rockchip: Wifi improvements for Sonoff iHost
:::::: branch date: 3 days ago
:::::: commit date: 3 days ago
config: arm-randconfig-052-20250429 (https://download.01.org/0day-ci/archive/20250430/202504300816.UPjewbSf-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
dtschema version: 2025.3.dev21+ge6ea659
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250430/202504300816.UPjewbSf-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/r/202504300816.UPjewbSf-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> arch/arm/boot/dts/rockchip/rv1109-sonoff-ihost.dtb: mmc@ffc70000 (rockchip,rv1126-dw-mshc): Unevaluated properties are not allowed ('supports-sdio' was unexpected)
from schema $id: http://devicetree.org/schemas/mmc/rockchip-dw-mshc.yaml#
--
>> arch/arm/boot/dts/rockchip/rv1126-sonoff-ihost.dtb: mmc@ffc70000 (rockchip,rv1126-dw-mshc): Unevaluated properties are not allowed ('supports-sdio' was unexpected)
from schema $id: http://devicetree.org/schemas/mmc/rockchip-dw-mshc.yaml#
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-04-30 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 0:23 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-27 6:50 ARM: dts: rockchip: Wifi improvements for Sonoff iHost Hao Zhang
2025-04-27 6:50 ` [PATCH 1/1] " Hao Zhang
2025-04-27 6:50 ` Hao Zhang
2025-04-27 11:14 ` Heiko Stübner
2025-04-27 11:14 ` Heiko Stübner
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=202504300816.UPjewbSf-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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 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.