From: kbuild test robot <fengguang.wu@intel.com>
To: Alexandre Bounine <alexandre.bounine@idt.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 4307/4657] arch/powerpc/sysdev/fsl_rmu.c:507:26: error: passing argument 1 of 'rio_inb_pwrite_handler' from incompatible pointer type
Date: Thu, 11 Feb 2016 19:03:40 +0800 [thread overview]
Message-ID: <201602111938.YTETCov4%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2814 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 8c8d01f13cc20965d084b7ddaecf96b9397aa66a
commit: 14cba476c99f4f75e8bf21bb6539649bd459882f [4307/4657] rapidio: add global inbound port write interfaces
config: powerpc-ppa8548_defconfig (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 14cba476c99f4f75e8bf21bb6539649bd459882f
# save the attached .config to linux build tree
make.cross ARCH=powerpc
All errors (new ones prefixed by >>):
arch/powerpc/sysdev/fsl_rmu.c: In function 'fsl_pw_dpc':
>> arch/powerpc/sysdev/fsl_rmu.c:507:26: error: passing argument 1 of 'rio_inb_pwrite_handler' from incompatible pointer type [-Werror=incompatible-pointer-types]
rio_inb_pwrite_handler((union rio_pw_msg *)msg_buffer);
^
In file included from arch/powerpc/sysdev/fsl_rio.h:31:0,
from arch/powerpc/sysdev/fsl_rmu.c:34:
include/linux/rio_drv.h:383:12: note: expected 'struct rio_mport *' but argument is of type 'union rio_pw_msg *'
extern int rio_inb_pwrite_handler(struct rio_mport *mport,
^
>> arch/powerpc/sysdev/fsl_rmu.c:507:3: error: too few arguments to function 'rio_inb_pwrite_handler'
rio_inb_pwrite_handler((union rio_pw_msg *)msg_buffer);
^
In file included from arch/powerpc/sysdev/fsl_rio.h:31:0,
from arch/powerpc/sysdev/fsl_rmu.c:34:
include/linux/rio_drv.h:383:12: note: declared here
extern int rio_inb_pwrite_handler(struct rio_mport *mport,
^
cc1: all warnings being treated as errors
vim +/rio_inb_pwrite_handler +507 arch/powerpc/sysdev/fsl_rmu.c
6ec4bedb Liu Gang 2011-11-12 501 pr_debug(" 0x%08x", msg_buffer[i]);
6ec4bedb Liu Gang 2011-11-12 502 }
6ec4bedb Liu Gang 2011-11-12 503 pr_debug("\n");
6ec4bedb Liu Gang 2011-11-12 504 }
6ec4bedb Liu Gang 2011-11-12 505 #endif
6ec4bedb Liu Gang 2011-11-12 506 /* Pass the port-write message to RIO core for processing */
6ec4bedb Liu Gang 2011-11-12 @507 rio_inb_pwrite_handler((union rio_pw_msg *)msg_buffer);
6ec4bedb Liu Gang 2011-11-12 508 }
6ec4bedb Liu Gang 2011-11-12 509 }
6ec4bedb Liu Gang 2011-11-12 510
:::::: The code at line 507 was first introduced by commit
:::::: 6ec4bedbf153a8ef71aeba99a40efef556b57798 fsl-rio: Split rio driver into two parts, RapidIO endpoint and message unit
:::::: TO: Liu Gang <Gang.Liu@freescale.com>
:::::: CC: Kumar Gala <galak@kernel.crashing.org>
---
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: 12369 bytes --]
reply other threads:[~2016-02-11 11:05 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=201602111938.YTETCov4%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexandre.bounine@idt.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