From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [ti:ti-android-linux-4.19.y 16322/18890] ion-ti.c:undefined reference to `ion_chunk_heap_create'
Date: Wed, 13 May 2020 14:44:51 +0800 [thread overview]
Message-ID: <202005131446.dCpstjtN%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
tree: git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-android-linux-4.19.y
head: 4ef4f96cd4cea91f1d1ac9168f182eccb3c34430
commit: c1e024d601864f25838348ff253b48dd9f7bc914 [16322/18890] Merge branch 'android-4.19' of https://android.googlesource.com/kernel/common into android-feature-ti-linux-4.19.y
config: riscv-allmodconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout c1e024d601864f25838348ff253b48dd9f7bc914
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
riscv64-linux-ld: drivers/staging/android/ion/ion-ti.o: in function `.L13':
>> ion-ti.c:(.init.text+0x178): undefined reference to `ion_chunk_heap_create'
riscv64-linux-ld: drivers/staging/android/ion/ion-ti.o: in function `.L11':
>> ion-ti.c:(.init.text+0x1a0): undefined reference to `ion_carveout_heap_create'
riscv64-linux-ld: drivers/staging/android/ion/ion-ti.o: in function `.L14':
>> ion-ti.c:(.init.text+0x1e0): undefined reference to `ion_device_add_heap'
---
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: 54823 bytes --]
reply other threads:[~2020-05-13 6:44 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=202005131446.dCpstjtN%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.