From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: add rock5 itx board
Date: Fri, 5 Jul 2024 12:37:56 +0800 [thread overview]
Message-ID: <202407051236.ppudG83Y-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "dtcheck: binding changes may go via different trees"
::::::
BCC: lkp@intel.com
CC: llvm@lists.linux.dev
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20240703210524.776455-3-heiko@sntech.de>
References: <20240703210524.776455-3-heiko@sntech.de>
TO: Heiko Stuebner <heiko@sntech.de>
TO: heiko@sntech.de
CC: robh@kernel.org
CC: krzk+dt@kernel.org
CC: conor+dt@kernel.org
CC: devicetree@vger.kernel.org
CC: linux-arm-kernel@lists.infradead.org
CC: linux-rockchip@lists.infradead.org
CC: linux-kernel@vger.kernel.org
Hi Heiko,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rockchip/for-next]
[also build test WARNING on soc/for-next next-20240703]
[cannot apply to robh/for-next arm/for-next arm/fixes arm64/for-next/core clk/clk-next kvmarm/next shawnguo/for-next linus/master v6.10-rc6]
[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/Heiko-Stuebner/dt-bindings-arm-rockchip-Add-Rock-5-ITX-board/20240705-012253
base: https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git for-next
patch link: https://lore.kernel.org/r/20240703210524.776455-3-heiko%40sntech.de
patch subject: [PATCH 2/2] arm64: dts: rockchip: add rock5 itx board
:::::: branch date: 11 hours ago
:::::: commit date: 11 hours ago
config: arm64-randconfig-002-20240705 (https://download.01.org/0day-ci/archive/20240705/202407051236.ppudG83Y-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project a0c6b8aef853eedaa0980f07c0a502a5a8a9740e)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240705/202407051236.ppudG83Y-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/202407051236.ppudG83Y-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> arch/arm64/boot/dts/rockchip/rk3588-rock-5itx.dts:1013.7-1021.4: Warning (graph_child_address): /usb@fc000000/port: graph node has single child node 'endpoint@0', #address-cells/#size-cells are not necessary
vim +1013 arch/arm64/boot/dts/rockchip/rk3588-rock-5itx.dts
792bbd3af10923 Heiko Stuebner 2024-07-03 1008
792bbd3af10923 Heiko Stuebner 2024-07-03 1009 &usb_host0_xhci {
792bbd3af10923 Heiko Stuebner 2024-07-03 1010 usb-role-switch;
792bbd3af10923 Heiko Stuebner 2024-07-03 1011 status = "okay";
792bbd3af10923 Heiko Stuebner 2024-07-03 1012
792bbd3af10923 Heiko Stuebner 2024-07-03 @1013 port {
792bbd3af10923 Heiko Stuebner 2024-07-03 1014 #address-cells = <1>;
792bbd3af10923 Heiko Stuebner 2024-07-03 1015 #size-cells = <0>;
792bbd3af10923 Heiko Stuebner 2024-07-03 1016
792bbd3af10923 Heiko Stuebner 2024-07-03 1017 dwc3_0_role_switch: endpoint@0 {
792bbd3af10923 Heiko Stuebner 2024-07-03 1018 reg = <0>;
792bbd3af10923 Heiko Stuebner 2024-07-03 1019 remote-endpoint = <&usbc0_role_sw>;
792bbd3af10923 Heiko Stuebner 2024-07-03 1020 };
792bbd3af10923 Heiko Stuebner 2024-07-03 1021 };
792bbd3af10923 Heiko Stuebner 2024-07-03 1022 };
792bbd3af10923 Heiko Stuebner 2024-07-03 1023
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-07-05 4:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 4:37 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-03 21:05 [PATCH 0/2] Rock 5 ITX devicetree Heiko Stuebner
2024-07-03 21:05 ` [PATCH 2/2] arm64: dts: rockchip: add rock5 itx board Heiko Stuebner
2024-07-03 21:05 ` Heiko Stuebner
2024-07-03 21:16 ` Dragan Simic
2024-07-03 21:16 ` Dragan Simic
2024-07-04 6:28 ` Krzysztof Kozlowski
2024-07-04 6:28 ` Krzysztof Kozlowski
2024-07-04 9:38 ` Diederik de Haas
2024-07-04 9:38 ` Diederik de Haas
2024-07-04 10:05 ` Heiko Stübner
2024-07-04 10:05 ` Heiko Stübner
2024-07-04 11:43 ` Alex Bee
2024-07-04 11:43 ` Alex Bee
2024-07-04 12:05 ` Heiko Stübner
2024-07-04 12:05 ` Heiko Stübner
2024-07-04 13:04 ` Alex Bee
2024-07-04 13:04 ` Alex Bee
2024-07-04 10:52 ` Alex Bee
2024-07-04 10:52 ` Alex Bee
2024-07-04 11:21 ` Heiko Stübner
2024-07-04 11:21 ` Heiko Stübner
2024-07-04 12:04 ` Dragan Simic
2024-07-04 12:04 ` Dragan Simic
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=202407051236.ppudG83Y-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.