From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v3] arm64: dts: imx8mm-emtop-baseboard: Add Peripherals Support
Date: Tue, 27 Aug 2024 01:59:03 +0800 [thread overview]
Message-ID: <202408270122.RS3dMlo8-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: arch/arm64/boot/dts/freescale/imx8mm-emtop-baseboard.dts:111.20-120.11: ERROR (phandle_references): /soc@0/bus@30800000/spba-bus@30800000/spi@30830000/can@0: Reference to non-existent node or label "pinctrl_canbus""
:::::: 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: <20240823120158.19294-1-tarang.raval@siliconsignals.io>
References: <20240823120158.19294-1-tarang.raval@siliconsignals.io>
TO: Tarang Raval <tarang.raval@siliconsignals.io>
TO: shawnguo@kernel.org
TO: krzk+dt@kernel.org
TO: festevam@gmail.com
CC: tarang.raval@siliconsignals.io
CC: Rob Herring <robh@kernel.org>
CC: Conor Dooley <conor+dt@kernel.org>
CC: Sascha Hauer <s.hauer@pengutronix.de>
CC: Pengutronix Kernel Team <kernel@pengutronix.de>
CC: devicetree@vger.kernel.org
CC: imx@lists.linux.dev
CC: linux-arm-kernel@lists.infradead.org
CC: linux-kernel@vger.kernel.org
Hi Tarang,
kernel test robot noticed the following build warnings:
[auto build test WARNING on shawnguo/for-next]
[also build test WARNING on next-20240826]
[cannot apply to linus/master v6.11-rc5]
[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/Tarang-Raval/arm64-dts-imx8mm-emtop-baseboard-Add-Peripherals-Support/20240826-125744
base: https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git for-next
patch link: https://lore.kernel.org/r/20240823120158.19294-1-tarang.raval%40siliconsignals.io
patch subject: [PATCH v3] arm64: dts: imx8mm-emtop-baseboard: Add Peripherals Support
:::::: branch date: 13 hours ago
:::::: commit date: 13 hours ago
config: arm64-defconfig (https://download.01.org/0day-ci/archive/20240827/202408270122.RS3dMlo8-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240827/202408270122.RS3dMlo8-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/202408270122.RS3dMlo8-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> arch/arm64/boot/dts/freescale/imx8mm-emtop-baseboard.dts:111.20-120.11: ERROR (phandle_references): /soc@0/bus@30800000/spba-bus@30800000/spi@30830000/can@0: Reference to non-existent node or label "pinctrl_canbus"
vim +/pinctrl_canbus +111 arch/arm64/boot/dts/freescale/imx8mm-emtop-baseboard.dts
d957ce2fca01e44 Tarang Raval 2024-08-23 104
d957ce2fca01e44 Tarang Raval 2024-08-23 105 /* CAN BUS */
d957ce2fca01e44 Tarang Raval 2024-08-23 106 &ecspi2 {
d957ce2fca01e44 Tarang Raval 2024-08-23 107 pinctrl-names = "default";
d957ce2fca01e44 Tarang Raval 2024-08-23 108 pinctrl-0 = <&pinctrl_ecspi2>;
d957ce2fca01e44 Tarang Raval 2024-08-23 109 status = "okay";
d957ce2fca01e44 Tarang Raval 2024-08-23 110
d957ce2fca01e44 Tarang Raval 2024-08-23 @111 can: can@0 {
d957ce2fca01e44 Tarang Raval 2024-08-23 112 compatible = "microchip,mcp2515";
d957ce2fca01e44 Tarang Raval 2024-08-23 113 reg = <0>;
d957ce2fca01e44 Tarang Raval 2024-08-23 114 pinctrl-names = "default";
d957ce2fca01e44 Tarang Raval 2024-08-23 115 pinctrl-0 = <&pinctrl_canbus>;
d957ce2fca01e44 Tarang Raval 2024-08-23 116 clocks = <&osc_can>;
d957ce2fca01e44 Tarang Raval 2024-08-23 117 interrupt-parent = <&gpio1>;
d957ce2fca01e44 Tarang Raval 2024-08-23 118 interrupts = <14 IRQ_TYPE_LEVEL_HIGH>;
d957ce2fca01e44 Tarang Raval 2024-08-23 119 spi-max-frequency = <10000000>;
d957ce2fca01e44 Tarang Raval 2024-08-23 120 };
38e93270fd735e6 Tarang Raval 2024-07-25 121 };
38e93270fd735e6 Tarang Raval 2024-07-25 122
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-08-26 17:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 17:59 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-23 12:01 [PATCH v3] arm64: dts: imx8mm-emtop-baseboard: Add Peripherals Support Tarang Raval
2024-08-23 12:36 ` Marc Kleine-Budde
2024-08-27 11:16 ` Tarang Raval
2024-08-27 12:01 ` Marc Kleine-Budde
2024-08-27 12:10 ` Fabio Estevam
2024-08-27 12:44 ` Tarang Raval
2024-09-01 7:58 ` Shawn Guo
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=202408270122.RS3dMlo8-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.