From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: oe-kbuild-all@lists.linux.dev, Lee Jones <lee.jones@linaro.org>,
Lee Jones <lee@kernel.org>
Subject: [lee-mfd:for-mfd-next 22/24] make[4]: *** No rule to make target 'drivers/mfd/htc-pasic3.o', needed by 'drivers/mfd/built-in.a'.
Date: Sat, 28 Jan 2023 20:34:13 +0800 [thread overview]
Message-ID: <202301282024.NcchLCFv-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
head: b8fe87f4ba9b3343e0682ce191cf33daa43039e8
commit: ff78a86f1bb2667ded7fa326a8b81e655476af32 [22/24] mfd: Remove htc-pasic3 driver
config: sparc-randconfig-r013-20230128 (https://download.01.org/0day-ci/archive/20230128/202301282024.NcchLCFv-lkp@intel.com/config)
compiler: sparc-linux-gcc (GCC) 12.1.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://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git/commit/?id=ff78a86f1bb2667ded7fa326a8b81e655476af32
git remote add lee-mfd https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
git fetch --no-tags lee-mfd for-mfd-next
git checkout ff78a86f1bb2667ded7fa326a8b81e655476af32
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=sparc olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=sparc SHELL=/bin/bash drivers/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> make[4]: *** No rule to make target 'drivers/mfd/htc-pasic3.o', needed by 'drivers/mfd/built-in.a'.
make[4]: Target 'drivers/mfd/' not remade because of errors.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-01-28 12:34 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=202301282024.NcchLCFv-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=lee.jones@linaro.org \
--cc=lee@kernel.org \
--cc=oe-kbuild-all@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.