From: kbuild test robot <fengguang.wu@intel.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 198/211] lib/dma-mapping.c:11: undefined reference to `bad_dma_ops'
Date: Fri, 17 Mar 2017 11:45:14 +0800 [thread overview]
Message-ID: <201703171106.LI5ZKxn3%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 8276ddb3c638602509386f1a05f75326dbf5ce09
commit: fcf58ec2015f30ac80f69138843007384d6aefc1 [198/211] include/linux/dma-mapping.h: uninline dma_alloc/free_attrs
config: um-x86_64_defconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout fcf58ec2015f30ac80f69138843007384d6aefc1
# save the attached .config to linux build tree
make ARCH=um SUBARCH=x86_64
All errors (new ones prefixed by >>):
kernel/built-in.o: In function `__atomic_add_unless':
include/asm-generic/atomic-instrumented.h:70: undefined reference to `__arch_atomic_add_unless'
include/asm-generic/atomic-instrumented.h:70: undefined reference to `__arch_atomic_add_unless'
include/asm-generic/atomic-instrumented.h:70: undefined reference to `__arch_atomic_add_unless'
include/asm-generic/atomic-instrumented.h:70: undefined reference to `__arch_atomic_add_unless'
include/asm-generic/atomic-instrumented.h:70: undefined reference to `__arch_atomic_add_unless'
mm/built-in.o:include/asm-generic/atomic-instrumented.h:70: more undefined references to `__arch_atomic_add_unless' follow
lib/lib.a(dma-mapping.o): In function `dma_alloc_attrs':
>> lib/dma-mapping.c:11: undefined reference to `bad_dma_ops'
lib/lib.a(dma-mapping.o): In function `dma_free_attrs':
lib/dma-mapping.c:34: undefined reference to `bad_dma_ops'
lib/dma-mapping.c:40: undefined reference to `bad_dma_ops'
collect2: error: ld returned 1 exit status
vim +11 lib/dma-mapping.c
5 dma_addr_t *dma_handle, gfp_t flag,
6 unsigned long attrs)
7 {
8 const struct dma_map_ops *ops = get_dma_ops(dev);
9 void *cpu_addr;
10
> 11 BUG_ON(!ops);
12
13 if (dma_alloc_from_coherent(dev, size, dma_handle, &cpu_addr))
14 return cpu_addr;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 7724 bytes --]
reply other threads:[~2017-03-17 3:46 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=201703171106.LI5ZKxn3%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox