From: kbuild test robot <lkp@intel.com>
To: Michael Moese <michael.moese@men.de>
Cc: kbuild-all@01.org, Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org,
Michael Moese <michael.moese@men.de>
Subject: Re: [PATCH] Introduce dmam_zalloc_coherent()
Date: Thu, 10 Aug 2017 01:44:13 +0800 [thread overview]
Message-ID: <201708100147.xc8uPU6V%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170808091535.31371-1-michael.moese@men.de>
[-- Attachment #1: Type: text/plain, Size: 2301 bytes --]
Hi Michael,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.13-rc4 next-20170808]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Michael-Moese/Introduce-dmam_zalloc_coherent/20170810-011949
config: i386-tinyconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from include/linux/skbuff.h:34:0,
from include/net/net_namespace.h:34,
from include/linux/inet.h:46,
from include/linux/sunrpc/msg_prot.h:203,
from include/linux/sunrpc/auth.h:15,
from include/linux/nfs_fs.h:29,
from init/do_mounts.c:32:
>> include/linux/dma-mapping.h:765:21: error: redefinition of 'dma_zalloc_coherent'
static inline void *dma_zalloc_coherent(struct device *dev, size_t size,
^~~~~~~~~~~~~~~~~~~
include/linux/dma-mapping.h:691:21: note: previous definition of 'dma_zalloc_coherent' was here
static inline void *dma_zalloc_coherent(struct device *dev, size_t size,
^~~~~~~~~~~~~~~~~~~
vim +/dma_zalloc_coherent +765 include/linux/dma-mapping.h
753
754 /*
755 * Managed DMA API
756 */
757 extern void *dmam_alloc_coherent(struct device *dev, size_t size,
758 dma_addr_t *dma_handle, gfp_t gfp);
759 extern void dmam_free_coherent(struct device *dev, size_t size, void *vaddr,
760 dma_addr_t dma_handle);
761 extern void *dmam_alloc_attrs(struct device *dev, size_t size,
762 dma_addr_t *dma_handle, gfp_t gfp,
763 unsigned long attrs);
764
> 765 static inline void *dma_zalloc_coherent(struct device *dev, size_t size,
766 dma_addr_t *dma_handle, gfp_t flag)
767 {
768 void *ret = dmam_alloc_coherent(dev, size, dma_handle,
769 flag | __GFP_ZERO);
770 return ret;
771 }
772
---
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: 6665 bytes --]
prev parent reply other threads:[~2017-08-09 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 9:15 Michael Moese
2017-08-09 13:37 ` Christoph Hellwig
2017-08-10 6:58 ` Marek Szyprowski
2017-08-09 17:44 ` kbuild test robot [this message]
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=201708100147.xc8uPU6V%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=michael.moese@men.de \
--cc=robin.murphy@arm.com \
/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
all inboxes | Powered by JetHome®