From: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 12118/12164] arch/x86/include/asm/dma-mapping.h:12:29: fatal error: linux/dma-attrs.h: No such file or directory
Date: Mon, 25 Jul 2016 20:24:42 +0800 [thread overview]
Message-ID: <201607252039.nncm7Vim%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2759 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: f7d63d99206b9ea674b6869f01ab68d651c717a2
commit: f48c41eedd53dd90c5fc37744932c806ece58b74 [12118/12164] dma-mapping: use unsigned long for dma_attrs
config: i386-tinyconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
git checkout f48c41eedd53dd90c5fc37744932c806ece58b74
# save the attached .config to linux build tree
make ARCH=i386
Note: the linux-next/master HEAD f7d63d99206b9ea674b6869f01ab68d651c717a2 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
In file included from include/linux/dma-mapping.h:132:0,
from include/linux/skbuff.h:34,
from include/linux/icmpv6.h:4,
from include/linux/ipv6.h:75,
from include/net/ipv6.h:16,
from include/linux/sunrpc/clnt.h:27,
from include/linux/nfs_fs.h:30,
from init/do_mounts.c:32:
>> arch/x86/include/asm/dma-mapping.h:12:29: fatal error: linux/dma-attrs.h: No such file or directory
#include <linux/dma-attrs.h>
^
compilation terminated.
vim +12 arch/x86/include/asm/dma-mapping.h
5872fb94 arch/x86/include/asm/dma-mapping.h Randy Dunlap 2009-01-29 6 * Documentation/DMA-API.txt for documentation.
6f536635 include/asm-x86/dma-mapping.h Glauber Costa 2008-03-25 7 */
6f536635 include/asm-x86/dma-mapping.h Glauber Costa 2008-03-25 8
d7002857 arch/x86/include/asm/dma-mapping.h Vegard Nossum 2008-07-20 9 #include <linux/kmemcheck.h>
6f536635 include/asm-x86/dma-mapping.h Glauber Costa 2008-03-25 10 #include <linux/scatterlist.h>
2118d0c5 arch/x86/include/asm/dma-mapping.h Joerg Roedel 2009-01-09 11 #include <linux/dma-debug.h>
abe6602b arch/x86/include/asm/dma-mapping.h FUJITA Tomonori 2009-01-05 @12 #include <linux/dma-attrs.h>
6f536635 include/asm-x86/dma-mapping.h Glauber Costa 2008-03-25 13 #include <asm/io.h>
6f536635 include/asm-x86/dma-mapping.h Glauber Costa 2008-03-25 14 #include <asm/swiotlb.h>
0a2b9a6e arch/x86/include/asm/dma-mapping.h Marek Szyprowski 2011-12-29 15 #include <linux/dma-contiguous.h>
:::::: The code at line 12 was first introduced by commit
:::::: abe6602bf197167efb3b37161b9c11748fa076e1 x86: add map_page and unmap_page to struct dma_mapping_ops
:::::: TO: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
:::::: CC: Ingo Molnar <mingo@elte.hu>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 6376 bytes --]
reply other threads:[~2016-07-25 12:25 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=201607252039.nncm7Vim%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=k.kozlowski@samsung.com \
--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