From: kernel test robot <lkp@intel.com>
To: Tudor Ambarus <tudor.ambarus@microchip.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [ambarus:spi-nor/id-collisions-v4 39/39] make[4]: *** No rule to make target 'drivers/mtd/spi-nor/xmc.o', needed by 'drivers/mtd/spi-nor/built-in.a'.
Date: Tue, 1 Mar 2022 05:10:57 +0800 [thread overview]
Message-ID: <202203010516.FbpMDFBg-lkp@intel.com> (raw)
tree: https://github.com/ambarus/linux-0day spi-nor/id-collisions-v4
head: 0dff6e52ceae6f25ba4afb713dde9bec6903fe72
commit: 0dff6e52ceae6f25ba4afb713dde9bec6903fe72 [39/39] mtd: spi-nor: Move XMC to manufacturer ID collisions driver
config: sh-randconfig-r001-20220228 (https://download.01.org/0day-ci/archive/20220301/202203010516.FbpMDFBg-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/ambarus/linux-0day/commit/0dff6e52ceae6f25ba4afb713dde9bec6903fe72
git remote add ambarus https://github.com/ambarus/linux-0day
git fetch --no-tags ambarus spi-nor/id-collisions-v4
git checkout 0dff6e52ceae6f25ba4afb713dde9bec6903fe72
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=sh SHELL=/bin/bash drivers/mtd/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> make[4]: *** No rule to make target 'drivers/mtd/spi-nor/xmc.o', needed by 'drivers/mtd/spi-nor/built-in.a'.
make[4]: Target '__build' not remade because of errors.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-28 21:11 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=202203010516.FbpMDFBg-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tudor.ambarus@microchip.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