From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [broonie-misc:asoc-5.11 143/145] xtensa-linux-ld: regmap-spi.c:undefined reference to `spi_sync'
Date: Tue, 01 Dec 2020 13:42:08 +0800 [thread overview]
Message-ID: <202012011306.VIyP4rYC-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3040 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git asoc-5.11
head: 645be01d7b553e9ab0791ceb88f381a087d691d9
commit: 6cd4c6459e47402ab90802eca61a18b231434053 [143/145] ASoC: Add ADAU1372 audio CODEC support
config: xtensa-randconfig-r006-20201201 (attached as .config)
compiler: xtensa-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/broonie/misc.git/commit/?id=6cd4c6459e47402ab90802eca61a18b231434053
git remote add broonie-misc https://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git
git fetch --no-tags broonie-misc asoc-5.11
git checkout 6cd4c6459e47402ab90802eca61a18b231434053
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=xtensa
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 >>):
xtensa-linux-ld: drivers/base/regmap/regmap-spi.o: in function `regmap_spi_async_alloc':
regmap-spi.c:(.text+0x20): undefined reference to `spi_write_then_read'
xtensa-linux-ld: drivers/base/regmap/regmap-spi.o: in function `regmap_spi_read':
regmap-spi.c:(.text+0x33): undefined reference to `spi_write_then_read'
xtensa-linux-ld: drivers/base/regmap/regmap-spi.o: in function `list_add_tail':
regmap-spi.c:(.text+0xa4): undefined reference to `spi_async'
xtensa-linux-ld: drivers/base/regmap/regmap-spi.o: in function `regmap_spi_async_write':
regmap-spi.c:(.text+0xef): undefined reference to `spi_async'
>> xtensa-linux-ld: regmap-spi.c:(.text+0x100): undefined reference to `spi_sync'
xtensa-linux-ld: drivers/base/regmap/regmap-spi.o: in function `regmap_spi_gather_write':
regmap-spi.c:(.text+0x142): undefined reference to `spi_sync'
xtensa-linux-ld: regmap-spi.c:(.text+0x14c): undefined reference to `spi_sync'
xtensa-linux-ld: drivers/base/regmap/regmap-spi.o: in function `spi_sync_transfer.constprop.0':
regmap-spi.c:(.text+0x166): undefined reference to `spi_sync'
>> xtensa-linux-ld: sound/soc/codecs/adau1372-spi.o:(.init.literal+0x4): undefined reference to `__spi_register_driver'
xtensa-linux-ld: sound/soc/codecs/adau1372-spi.o: in function `adau1372_spi_probe':
adau1372-spi.c:(.text+0x60): undefined reference to `spi_write_then_read'
xtensa-linux-ld: sound/soc/codecs/adau1372-spi.o: in function `spi_w8r8.constprop.0':
adau1372-spi.c:(.text+0x7a): undefined reference to `spi_write_then_read'
xtensa-linux-ld: sound/soc/codecs/adau1372-spi.o: in function `adau1372_spi_driver_init':
adau1372-spi.c:(.init.text+0xa): undefined reference to `__spi_register_driver'
---
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: 26154 bytes --]
reply other threads:[~2020-12-01 5:42 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=202012011306.VIyP4rYC-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.