From: kernel test robot <lkp@intel.com>
To: Thierry Reding <treding@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [linux-next:master 8617/9935] arch/arm64/boot/dts/nvidia/tegra264.dtsi:3:10: fatal error: dt-bindings/clock/nvidia,tegra264.h: No such file or directory
Date: Wed, 16 Jul 2025 18:39:40 +0800 [thread overview]
Message-ID: <202507161859.qKPDbuJq-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: f2b1f6a9f382564b1d4cf16c45e73ccccb917f1f
commit: d01e4f1e7aa8833f549ac61a0bbcdc395533269b [8617/9935] arm64: tegra: Add p3971-0089+p3834-0008 support
config: arm64-randconfig-051-20250716 (https://download.01.org/0day-ci/archive/20250716/202507161859.qKPDbuJq-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 8.5.0
dtschema version: 2025.6.2.dev4+g8f79ddd
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250716/202507161859.qKPDbuJq-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/202507161859.qKPDbuJq-lkp@intel.com/
Note: the linux-next/master HEAD f2b1f6a9f382564b1d4cf16c45e73ccccb917f1f builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
In file included from arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi:3,
from arch/arm64/boot/dts/nvidia/tegra264-p3834-0008.dtsi:3,
from arch/arm64/boot/dts/nvidia/tegra264-p3971-0089+p3834-0008.dts:5:
>> arch/arm64/boot/dts/nvidia/tegra264.dtsi:3:10: fatal error: dt-bindings/clock/nvidia,tegra264.h: No such file or directory
3 | #include <dt-bindings/clock/nvidia,tegra264.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
dtcheck warnings: (new ones prefixed by >>)
>> In file included from arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi:3,
>> from arch/arm64/boot/dts/nvidia/tegra264-p3834-0008.dtsi:3,
>> from arch/arm64/boot/dts/nvidia/tegra264-p3971-0089+p3834-0008.dts:5:
arch/arm64/boot/dts/nvidia/tegra264.dtsi:3:10: fatal error: dt-bindings/clock/nvidia,tegra264.h: No such file or directory
3 | #include <dt-bindings/clock/nvidia,tegra264.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +3 arch/arm64/boot/dts/nvidia/tegra264.dtsi
65ef237e4810f6 Thierry Reding 2025-07-10 2
65ef237e4810f6 Thierry Reding 2025-07-10 @3 #include <dt-bindings/clock/nvidia,tegra264.h>
65ef237e4810f6 Thierry Reding 2025-07-10 4 #include <dt-bindings/interrupt-controller/arm-gic.h>
65ef237e4810f6 Thierry Reding 2025-07-10 5 #include <dt-bindings/mailbox/tegra186-hsp.h>
b7117911e13cf5 Thierry Reding 2025-07-10 6 #include <dt-bindings/memory/nvidia,tegra264.h>
65ef237e4810f6 Thierry Reding 2025-07-10 7 #include <dt-bindings/reset/nvidia,tegra264.h>
65ef237e4810f6 Thierry Reding 2025-07-10 8
:::::: The code at line 3 was first introduced by commit
:::::: 65ef237e4810f6bb0f44b250d963b48790dec369 arm64: tegra: Add Tegra264 support
:::::: TO: Thierry Reding <treding@nvidia.com>
:::::: CC: Thierry Reding <treding@nvidia.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-16 10:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202507161859.qKPDbuJq-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=treding@nvidia.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.