From: kernel test robot <lkp@intel.com>
To: Pratyush Yadav <p.yadav@ti.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: [ti:ti-rt-linux-5.10.y 3916/10108] arc-elf-ld: spi-cadence-quadspi.c:undefined reference to `spi_mem_exec_op'
Date: Mon, 25 Oct 2021 17:09:29 +0800 [thread overview]
Message-ID: <202110251723.isWAZ6H8-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]
tree: git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-rt-linux-5.10.y
head: b9f28fcb222bc4508077366b05ad5d44984087b0
commit: be58a6d2184f996fa51cb83c98426fd634606d63 [3916/10108] spi: cadence-qspi: Tune PHY to allow running at higher frequencies
config: arc-randconfig-r043-20211025 (attached as .config)
compiler: arc-elf-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
git remote add ti git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
git fetch --no-tags ti ti-rt-linux-5.10.y
git checkout be58a6d2184f996fa51cb83c98426fd634606d63
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arc SHELL=/bin/bash
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 >>):
arc-elf-ld: drivers/spi/spi-cadence-quadspi.o: in function `cqspi_phy_check_pattern':
spi-cadence-quadspi.c:(.text+0x1e6): undefined reference to `spi_mem_exec_op'
>> arc-elf-ld: spi-cadence-quadspi.c:(.text+0x1e6): undefined reference to `spi_mem_exec_op'
---
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: 27863 bytes --]
reply other threads:[~2021-10-25 9:10 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=202110251723.isWAZ6H8-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.yadav@ti.com \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®