From: kbuild test robot <lkp@intel.com>
To: Zhao Qiang <qiang.zhao@nxp.com>
Cc: kbuild-all@01.org, davem@davemloft.net, oss@buserror.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
xiaobo.xie@nxp.com, Zhao Qiang <qiang.zhao@nxp.com>
Subject: Re: [PATCH] Maxim/driver: Add driver for maxim ds26522
Date: Thu, 23 Jun 2016 11:34:22 +0800 [thread overview]
Message-ID: <201606231100.YBm9kbtW%fengguang.wu@intel.com> (raw)
In-Reply-To: <1466644185-6081-1-git-send-email-qiang.zhao@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2662 bytes --]
Hi,
[auto build test ERROR on net-next/master]
[also build test ERROR on next-20160622]
[cannot apply to v4.7-rc4]
[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/Zhao-Qiang/Maxim-driver-Add-driver-for-maxim-ds26522/20160623-095007
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All error/warnings (new ones prefixed by >>):
In file included from include/linux/module.h:18:0,
from drivers/net/wan/slic_ds26522.c:15:
>> drivers/net/wan/slic_ds26522.c:39:20: error: expected ',' or ';' before 'DRV_DESC'
MODULE_DESCRIPTION(DRV_DESC);
^
include/linux/moduleparam.h:23:26: note: in definition of macro '__MODULE_INFO'
= __stringify(tag) "=" info
^~~~
>> include/linux/module.h:218:42: note: in expansion of macro 'MODULE_INFO'
#define MODULE_DESCRIPTION(_description) MODULE_INFO(description, _description)
^~~~~~~~~~~
>> drivers/net/wan/slic_ds26522.c:39:1: note: in expansion of macro 'MODULE_DESCRIPTION'
MODULE_DESCRIPTION(DRV_DESC);
^~~~~~~~~~~~~~~~~~
vim +39 drivers/net/wan/slic_ds26522.c
9 * under the terms of the GNU General Public License as published by the
10 * Free Software Foundation; either version 2 of the License, or (at your
11 * option) any later version.
12 */
13
14 #include <linux/bitrev.h>
> 15 #include <linux/module.h>
16 #include <linux/device.h>
17 #include <linux/kernel.h>
18 #include <linux/sched.h>
19 #include <linux/kthread.h>
20 #include <linux/spi/spi.h>
21 #include <linux/wait.h>
22 #include <linux/param.h>
23 #include <linux/delay.h>
24 #include <linux/of.h>
25 #include <linux/of_address.h>
26 #include <linux/io.h>
27 #include "slic_ds26522.h"
28
29 #define DRV_NAME "ds26522"
30
31 #define SLIC_TRANS_LEN 1
32 #define SLIC_TWO_LEN 2
33 #define SLIC_THREE_LEN 3
34
35 static struct spi_device *g_spi;
36
37 MODULE_LICENSE("GPL");
38 MODULE_AUTHOR("Zhao Qiang<B45475@freescale.com>");
> 39 MODULE_DESCRIPTION(DRV_DESC);
40
41 /* the read/write format of address is
42 * w/r|A13|A12|A11|A10|A9|A8|A7|A6|A5|A4|A3|A2|A1|A0|x
---
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: 55049 bytes --]
next prev parent reply other threads:[~2016-06-23 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 1:09 [PATCH] Maxim/driver: Add driver for maxim ds26522 Zhao Qiang
2016-06-23 3:34 ` kbuild test robot [this message]
2016-06-23 14:59 ` David Miller
2016-06-24 2:00 ` Qiang Zhao
2016-06-24 19:46 ` David Miller
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=201606231100.YBm9kbtW%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss@buserror.net \
--cc=qiang.zhao@nxp.com \
--cc=xiaobo.xie@nxp.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;
as well as URLs for NNTP newsgroup(s).