From: kbuild test robot <lkp@intel.com>
To: Max Staudt <mstaudt@suse.de>
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org, mstaudt@suse.de,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 8250: option 'force_polling' for buggy IRQs
Date: Tue, 26 Jul 2016 02:19:03 +0800 [thread overview]
Message-ID: <201607260241.cWzeZvYH%fengguang.wu@intel.com> (raw)
In-Reply-To: <1469468175-15704-1-git-send-email-mstaudt@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]
Hi,
[auto build test ERROR on tty/tty-testing]
[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/Max-Staudt/8250-option-force_polling-for-buggy-IRQs/20160726-013812
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
config: x86_64-randconfig-x012-201630 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/tty/serial/8250/8250_core.c: In function 's8250_options':
>> drivers/tty/serial/8250/8250_core.c:1250:43: error: macro "module_param_cb" requires 4 arguments, but only 3 given
module_param_cb(force_polling, uint, 0644);
^
>> drivers/tty/serial/8250/8250_core.c:1250:2: error: 'module_param_cb' undeclared (first use in this function)
module_param_cb(force_polling, uint, 0644);
^~~~~~~~~~~~~~~
drivers/tty/serial/8250/8250_core.c:1250:2: note: each undeclared identifier is reported only once for each function it appears in
vim +/module_param_cb +1250 drivers/tty/serial/8250/8250_core.c
1244 #undef MODULE_PARAM_PREFIX
1245 #define MODULE_PARAM_PREFIX "8250_core."
1246
1247 module_param_cb(share_irqs, ¶m_ops_uint, &share_irqs, 0644);
1248 module_param_cb(nr_uarts, ¶m_ops_uint, &nr_uarts, 0644);
1249 module_param_cb(skip_txen_test, ¶m_ops_uint, &skip_txen_test, 0644);
> 1250 module_param_cb(force_polling, uint, 0644);
1251 #ifdef CONFIG_SERIAL_8250_RSA
1252 __module_param_call(MODULE_PARAM_PREFIX, probe_rsa,
1253 ¶m_array_ops, .arr = &__param_arr_probe_rsa,
---
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: 18880 bytes --]
next prev parent reply other threads:[~2016-07-25 18:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 17:36 [PATCH] 8250: option 'force_polling' for buggy IRQs Max Staudt
2016-07-25 17:47 ` Greg KH
2016-07-26 11:42 ` Max Staudt
2016-07-26 15:08 ` Greg KH
2016-07-26 16:18 ` Max Staudt
2016-07-27 12:09 ` One Thousand Gnomes
2016-07-27 12:14 ` Max Staudt
2016-07-27 13:33 ` Theodore Ts'o
2016-07-27 20:01 ` One Thousand Gnomes
2016-07-28 9:59 ` Max Staudt
2016-07-28 14:47 ` Greg KH
2016-07-28 16:01 ` Theodore Ts'o
2016-07-28 18:40 ` Eric W. Biederman
2016-07-29 9:23 ` One Thousand Gnomes
2016-07-29 9:58 ` Max Staudt
2016-07-29 17:38 ` Eric W. Biederman
2016-08-01 15:27 ` One Thousand Gnomes
2016-07-25 18:19 ` kbuild test robot [this message]
2016-07-26 11:47 ` [PATCHv2] " Max Staudt
2016-07-26 11:54 ` [PATCHv3] " Max Staudt
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=201607260241.cWzeZvYH%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mstaudt@suse.de \
/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).