From: kernel test robot <lkp@intel.com>
To: Richard Kuo <rkuo@quicinc.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Brian Cain <bcain@kernel.org>
Subject: [bcain:bcain/boot_qemu 20/38] make[4]: *** No rule to make target 'arch/hexagon/boot/dts/msm8960_fluid.dtb', needed by 'arch/hexagon/boot/dts/'.
Date: Wed, 28 Jan 2026 07:27:30 +0800 [thread overview]
Message-ID: <202601280710.78BAV0sX-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/bcain/linux.git bcain/boot_qemu
head: 6dd00eeb9163d38cdab8b12c40702a711f04a9ab
commit: 78951630122eae2f9915fda71077ecd729f34ff0 [20/38] hexagon: update build system and Kconfig
config: hexagon-randconfig-001-20260128 (https://download.01.org/0day-ci/archive/20260128/202601280710.78BAV0sX-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260128/202601280710.78BAV0sX-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/202601280710.78BAV0sX-lkp@intel.com/
All errors (new ones prefixed by >>):
>> make[4]: *** No rule to make target 'arch/hexagon/boot/dts/msm8960_fluid.dtb', needed by 'arch/hexagon/boot/dts/'.
make[4]: Target 'arch/hexagon/boot/dts/' not remade because of errors.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for DEBUG_GPIO
Depends on [n]: GPIOLIB [=y] && DEBUG_KERNEL [=n]
Selected by [y]:
- HEXAGON_MSM8960_FLUID [=y]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-27 23:28 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=202601280710.78BAV0sX-lkp@intel.com \
--to=lkp@intel.com \
--cc=bcain@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rkuo@quicinc.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