From: kbuild test robot <lkp@intel.com>
To: vaibhavddit@gmail.com
Cc: kbuild-all@01.org, thomas.petazzoni@free-electrons.com,
devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
Vaibhav Kothari <vaibhavddit@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] drivers: staging: fbtft: Hush Checkpatch.pl Error about unnecessary whitespace and comma
Date: Thu, 30 Mar 2017 06:55:45 +0800 [thread overview]
Message-ID: <201703300659.daSwHkTv%fengguang.wu@intel.com> (raw)
In-Reply-To: <1490770381-3082-1-git-send-email-vaibhavddit@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5236 bytes --]
Hi Vaibhav,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.11-rc4 next-20170329]
[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/vaibhavddit-gmail-com/drivers-staging-fbtft-Hush-Checkpatch-pl-Error-about-unnecessary-whitespace-and-comma/20170330-063109
config: x86_64-randconfig-x009-201713 (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 >>):
>> drivers/staging/fbtft/fbtft-bus.c:59:49: error: macro "define_fbtft_write_reg" requires 3 arguments, but only 2 given
define_fbtft_write_reg(fbtft_write_reg8_bus8, u8)
^
>> drivers/staging/fbtft/fbtft-bus.c:14:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'
void func(struct fbtft_par *par, int len, ...) \
^
drivers/staging/fbtft/fbtft-bus.c:60:1: note: in expansion of macro 'define_fbtft_write_reg'
define_fbtft_write_reg(fbtft_write_reg16_bus8, u16, cpu_to_be16)
^~~~~~~~~~~~~~~~~~~~~~
drivers/staging/fbtft/fbtft-bus.c:61:52: error: macro "define_fbtft_write_reg" requires 3 arguments, but only 2 given
define_fbtft_write_reg(fbtft_write_reg16_bus16, u16)
^
drivers/staging/fbtft/fbtft-bus.c:63:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'
void fbtft_write_reg8_bus9(struct fbtft_par *par, int len, ...)
^~~~
vim +/define_fbtft_write_reg +59 drivers/staging/fbtft/fbtft-bus.c
8 *
9 * void (*write_reg)(struct fbtft_par *par, int len, ...);
10 *
11 *****************************************************************************/
12
13 #define define_fbtft_write_reg(func, type, modifier) \
> 14 void func(struct fbtft_par *par, int len, ...) \
15 { \
16 va_list args; \
17 int i, ret; \
18 int offset = 0; \
19 type *buf = (type *)par->buf; \
20 \
21 if (unlikely(par->debug & DEBUG_WRITE_REGISTER)) { \
22 va_start(args, len); \
23 for (i = 0; i < len; i++) { \
24 buf[i] = (type)va_arg(args, unsigned int); \
25 } \
26 va_end(args); \
27 fbtft_par_dbg_hex(DEBUG_WRITE_REGISTER, par, par->info->device, type, buf, len, "%s: ", __func__); \
28 } \
29 \
30 va_start(args, len); \
31 \
32 if (par->startbyte) { \
33 *(u8 *)par->buf = par->startbyte; \
34 buf = (type *)(par->buf + 1); \
35 offset = 1; \
36 } \
37 \
38 *buf = modifier((type)va_arg(args, unsigned int)); \
39 ret = fbtft_write_buf_dc(par, par->buf, sizeof(type) + offset, 0); \
40 if (ret < 0) \
41 goto out; \
42 len--; \
43 \
44 if (par->startbyte) \
45 *(u8 *)par->buf = par->startbyte | 0x2; \
46 \
47 if (len) { \
48 i = len; \
49 while (i--) \
50 *buf++ = modifier((type)va_arg(args, unsigned int)); \
51 fbtft_write_buf_dc(par, par->buf, \
52 len * (sizeof(type) + offset), 1); \
53 } \
54 out: \
55 va_end(args); \
56 } \
57 EXPORT_SYMBOL(func);
58
> 59 define_fbtft_write_reg(fbtft_write_reg8_bus8, u8)
60 define_fbtft_write_reg(fbtft_write_reg16_bus8, u16, cpu_to_be16)
61 define_fbtft_write_reg(fbtft_write_reg16_bus16, u16)
62
---
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: 29016 bytes --]
prev parent reply other threads:[~2017-03-29 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 6:53 vaibhavddit
2017-03-29 7:08 ` Greg KH
2017-03-29 22:55 ` 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=201703300659.daSwHkTv%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=vaibhavddit@gmail.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®