From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [android-common:android11-5.4 8964/10056] ld.lld: error: undefined symbol: dvb_register_frontend
Date: Mon, 28 Dec 2020 08:36:49 +0800 [thread overview]
Message-ID: <202012280843.JdtWLikm-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]
Hi Greg,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android11-5.4
head: 8038bc2bb90a14027e85669553263cfc6468ac9d
commit: a35cf7283648f203669736b32dac0f5706e02944 [8964/10056] ANDROID: GKI: Fix up "do not export symbol_get/put()" commit
config: x86_64-randconfig-a012-20201221 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project cee1e7d14f4628d6174b33640d502bff3b54ae45)
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
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
git remote add android-common https://android.googlesource.com/kernel/common
git fetch --no-tags android-common android11-5.4
git checkout a35cf7283648f203669736b32dac0f5706e02944
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
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 >>):
>> ld.lld: error: undefined symbol: dvb_register_frontend
>>> referenced by cxd2880-spi.c:558 (drivers/media/spi/cxd2880-spi.c:558)
>>> media/spi/cxd2880-spi.o:(cxd2880_spi_probe) in archive drivers/built-in.a
---
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: 36380 bytes --]
reply other threads:[~2020-12-28 0:36 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=202012280843.JdtWLikm-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.