From: kbuild test robot <lkp@intel.com>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: kbuild-all@01.org, arnaud.patard@rtp-net.org,
devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] staging: xgifb: function definition argument should have an identifier name
Date: Wed, 22 Feb 2017 04:50:53 +0800 [thread overview]
Message-ID: <201702220417.ZH4KbKpZ%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170221180852.GA19723@arushi-HP-Pavilion-Notebook>
[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]
Hi Arushi,
[auto build test ERROR on v4.9-rc8]
[cannot apply to staging/staging-testing next-20170220]
[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/Arushi-Singhal/staging-xgifb-function-definition-argument-should-have-an-identifier-name/20170222-031312
config: x86_64-randconfig-ne0-02220257 (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=x86_64
All errors (new ones prefixed by >>):
In file included from drivers/staging/xgifb/XGI_main_26.c:16:0:
>> drivers/staging/xgifb/vb_setmode.h:11:11: error: expected '=', ',', ';', 'asm' or '__attribute__' before '->' token
pVBInfo->VBInfo = DisableCRT2Display;
^~
vim +11 drivers/staging/xgifb/vb_setmode.h
5 void XGI_UnLockCRT2(struct vb_device_info *pVBInfo);
6 void XGI_LockCRT2(struct vb_device_info *pVBInfo);
7 void XGI_DisplayOff(struct xgifb_video_info *xgifb_info,
8 struct xgi_hw_device_info *pXGIHWDE,
9 struct vb_device_info *pVBInfo);
10 void XGI_GetVBType(struct vb_device_info *pVBInfo);
> 11 pVBInfo->VBInfo = DisableCRT2Display;
12 void XGI_SenseCRT1(struct vb_device_info *pVBInfo);
13 unsigned char XGISetModeNew(struct xgifb_video_info *xgifb_info,
14 struct xgi_hw_device_info *HwDeviceExtension,
---
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: 25266 bytes --]
prev parent reply other threads:[~2017-02-21 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 18:08 Arushi Singhal
2017-02-21 18:13 ` [Outreachy kernel] " Julia Lawall
2017-02-21 20:50 ` 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=201702220417.ZH4KbKpZ%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=arnaud.patard@rtp-net.org \
--cc=arushisinghal19971997@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.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®