From: kbuild test robot <fengguang.wu@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org
Subject: [vfs:work.pages 80/80] arch/m68k/sun3x/dvma.c:147:5: error: conflicting types for 'dvma_map_iommu'
Date: Mon, 21 Dec 2015 06:57:05 +0800 [thread overview]
Message-ID: <201512210603.updPB4Oh%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.pages
head: b38f3a2b9287eeea9c8ab2e0e839035628662270
commit: b38f3a2b9287eeea9c8ab2e0e839035628662270 [80/80] [sun3] try to sort dvma types out
config: m68k-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout b38f3a2b9287eeea9c8ab2e0e839035628662270
# save the attached .config to linux build tree
make.cross ARCH=m68k
All error/warnings (new ones prefixed by >>):
arch/m68k/sun3/sun3dvma.c: In function 'dvma_map_align':
>> arch/m68k/sun3/sun3dvma.c:312:7: warning: passing argument 1 of 'dvma_map_iommu' makes integer from pointer without a cast
if (!dvma_map_iommu(kaddr, baddr, len))
^
In file included from arch/m68k/sun3/sun3dvma.c:19:0:
arch/m68k/include/asm/dvma.h:19:12: note: expected 'long unsigned int' but argument is of type 'void *'
extern int dvma_map_iommu(unsigned long kaddr, unsigned long baddr,
^
--
>> arch/m68k/sun3x/dvma.c:147:5: error: conflicting types for 'dvma_map_iommu'
int dvma_map_iommu(void *kaddr, unsigned long baddr, int len)
^
In file included from arch/m68k/sun3x/dvma.c:21:0:
arch/m68k/include/asm/dvma.h:19:12: note: previous declaration of 'dvma_map_iommu' was here
extern int dvma_map_iommu(unsigned long kaddr, unsigned long baddr,
^
vim +/dvma_map_iommu +147 arch/m68k/sun3x/dvma.c
141
142 out:
143 return ret;
144 }
145
146
> 147 int dvma_map_iommu(void *kaddr, unsigned long baddr, int len)
148 {
149 unsigned long end, index;
150
---
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: 35262 bytes --]
reply other threads:[~2015-12-20 22:57 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=201512210603.updPB4Oh%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.