From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [hch-misc:dma-inline-remap.2 5/5] direct.c:undefined reference to `arch_dma_prep_coherent'
Date: Sat, 22 Feb 2020 07:50:19 +0800 [thread overview]
Message-ID: <202002220711.mrIXRiu3%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
tree: git://git.infradead.org/users/hch/misc.git dma-inline-remap.2
head: 099575d1501796e13f502a8002489f150adf4f33
commit: 099575d1501796e13f502a8002489f150adf4f33 [5/5] openrisc: use the generic in-place uncached DMA allocator
config: openrisc-simple_smp_defconfig (attached as .config)
compiler: or1k-linux-gcc (GCC) 9.2.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 099575d1501796e13f502a8002489f150adf4f33
# save the attached .config to linux build tree
GCC_VERSION=9.2.0 make.cross ARCH=openrisc
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
or1k-linux-ld: kernel/dma/direct.o: in function `dma_direct_alloc_pages':
>> direct.c:(.text+0x95c): undefined reference to `arch_dma_prep_coherent'
direct.c:(.text+0x95c): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `arch_dma_prep_coherent'
>> or1k-linux-ld: direct.c:(.text+0x9d4): undefined reference to `arch_dma_prep_coherent'
direct.c:(.text+0x9d4): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `arch_dma_prep_coherent'
---
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: 8096 bytes --]
reply other threads:[~2020-02-21 23:50 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=202002220711.mrIXRiu3%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.