From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-next:master 3035/6048] sh4-linux-nm: 'drivers/soc/litex/litex_soc_ctrl.o': No such file
Date: Tue, 26 Jan 2021 11:15:23 +0800 [thread overview]
Message-ID: <202101261118.GbbYSlHu-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 59fa6a163ffabc1bf25c5e0e33899e268a96d3cc
commit: 9d93a9e8aab3f82b6742dd034a6a81d4025cd82e [3035/6048] drivers/soc/litex: move generic accessors to litex.h
config: sh-randconfig-r025-20210125 (attached as .config)
compiler: sh4-linux-gcc (GCC) 9.3.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/next/linux-next.git/commit/?id=9d93a9e8aab3f82b6742dd034a6a81d4025cd82e
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 9d93a9e8aab3f82b6742dd034a6a81d4025cd82e
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=sh
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 >>):
>> sh4-linux-nm: 'drivers/soc/litex/litex_soc_ctrl.o': No such file
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 24272 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Gabriel Somlo <gsomlo@gmail.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Stafford Horne <shorne@gmail.com>
Subject: [linux-next:master 3035/6048] sh4-linux-nm: 'drivers/soc/litex/litex_soc_ctrl.o': No such file
Date: Tue, 26 Jan 2021 11:15:23 +0800 [thread overview]
Message-ID: <202101261118.GbbYSlHu-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 59fa6a163ffabc1bf25c5e0e33899e268a96d3cc
commit: 9d93a9e8aab3f82b6742dd034a6a81d4025cd82e [3035/6048] drivers/soc/litex: move generic accessors to litex.h
config: sh-randconfig-r025-20210125 (attached as .config)
compiler: sh4-linux-gcc (GCC) 9.3.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/next/linux-next.git/commit/?id=9d93a9e8aab3f82b6742dd034a6a81d4025cd82e
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 9d93a9e8aab3f82b6742dd034a6a81d4025cd82e
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=sh
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 >>):
>> sh4-linux-nm: 'drivers/soc/litex/litex_soc_ctrl.o': No such file
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 24272 bytes --]
next reply other threads:[~2021-01-26 3:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 3:15 kernel test robot [this message]
2021-01-26 3:15 ` [linux-next:master 3035/6048] sh4-linux-nm: 'drivers/soc/litex/litex_soc_ctrl.o': No such file kernel test robot
2021-01-28 4:05 ` Souptick Joarder
2021-02-08 6:29 ` Rong Chen
2021-02-08 6:29 ` Rong Chen
2021-02-10 15:04 ` [PATCH] scripts/recordmcount.pl: support big endian for ARCH sh Rong Chen
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=202101261118.GbbYSlHu-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.