From: kernel test robot <lkp@intel.com>
To: Paresh Bhagat <p-bhagat@ti.com>,
nm@ti.com, vigneshr@ti.com, praneeth@ti.com
Cc: oe-kbuild-all@lists.linux.dev, kristo@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, khasim@ti.com, v-singh1@ti.com,
afd@ti.com
Subject: Re: [PATCH 3/3] arm64: dts: ti: Add support for AM62D2-EVM
Date: Fri, 2 May 2025 10:04:54 +0800 [thread overview]
Message-ID: <202505020921.tGSgIFVU-lkp@intel.com> (raw)
In-Reply-To: <20250501072923.1262414-4-p-bhagat@ti.com>
Hi Paresh,
kernel test robot noticed the following build errors:
[auto build test ERROR on robh/for-next]
[also build test ERROR on linus/master v6.15-rc4 next-20250501]
[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/Paresh-Bhagat/dt-bindings-arm-ti-Add-bindings-for-AM62D2-SoC/20250501-153150
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20250501072923.1262414-4-p-bhagat%40ti.com
patch subject: [PATCH 3/3] arm64: dts: ti: Add support for AM62D2-EVM
config: arm64-randconfig-003-20250502 (https://download.01.org/0day-ci/archive/20250502/202505020921.tGSgIFVU-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250502/202505020921.tGSgIFVU-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/202505020921.tGSgIFVU-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/arm64/boot/dts/ti/k3-am62d2-evm.dts:15:10: fatal error: k3-timesync-router.h: No such file or directory
15 | #include "k3-timesync-router.h"
| ^~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +15 arch/arm64/boot/dts/ti/k3-am62d2-evm.dts
14
> 15 #include "k3-timesync-router.h"
16
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-02 2:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 7:29 [PATCH 0/3] Add support for AM62D2 SoC and EVM Paresh Bhagat
2025-05-01 7:29 ` [PATCH 1/3] dt-bindings: arm: ti: Add bindings for AM62D2 SoC Paresh Bhagat
2025-05-01 8:27 ` Rob Herring (Arm)
2025-05-01 7:29 ` [PATCH 2/3] arm64: dts: ti: Add pinctrl entries for AM62D2 family of SoCs Paresh Bhagat
2025-05-01 7:29 ` [PATCH 3/3] arm64: dts: ti: Add support for AM62D2-EVM Paresh Bhagat
2025-05-02 2:04 ` kernel test robot [this message]
2025-05-02 10:07 ` 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=202505020921.tGSgIFVU-lkp@intel.com \
--to=lkp@intel.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khasim@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=p-bhagat@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=v-singh1@ti.com \
--cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox