From: kbuild test robot <lkp@intel.com>
To: Jia He <hejianet@gmail.com>
Cc: kbuild-all@01.org, linux-nfs@vger.kernel.org,
"J. Bruce Fields" <bfields@fieldses.org>,
Jeff Layton <jlayton@poochiereds.net>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
linux-kernel@vger.kernel.org, Jia He <hejianet@gmail.com>
Subject: Re: [PATCH v2 1/1] lockd: Change nsm_use_hostnames from bool to u32
Date: Mon, 12 Dec 2016 20:54:37 +0800 [thread overview]
Message-ID: <201612122048.tetBugcc%fengguang.wu@intel.com> (raw)
In-Reply-To: <1481470609-31488-2-git-send-email-hejianet@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3303 bytes --]
Hi Jia,
[auto build test ERROR on nfsd/nfsd-next]
[also build test ERROR on v4.9 next-20161209]
[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/Jia-He/lockd-Change-nsm_use_hostnames-from-bool-to-u32/20161212-001614
base: git://linux-nfs.org/~bfields/linux.git nfsd-next
config: x86_64-kexec (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 include/linux/module.h:18:0,
from fs/lockd/svc.c:15:
>> include/linux/moduleparam.h:146:27: error: expected ')' before '&' token
param_check_##type(name, &(value)); \
^
include/linux/moduleparam.h:126:2: note: in expansion of macro 'module_param_named'
module_param_named(name, name, type, perm)
^~~~~~~~~~~~~~~~~~
fs/lockd/svc.c:661:1: note: in expansion of macro 'module_param'
module_param(nsm_use_hostnames, u32, 0644);
^~~~~~~~~~~~
>> include/linux/moduleparam.h:147:25: error: 'param_ops_u32' undeclared here (not in a function)
module_param_cb(name, ¶m_ops_##type, &value, perm); \
^
include/linux/moduleparam.h:224:39: note: in definition of macro '__module_param_call'
= { __param_str_##name, THIS_MODULE, ops, \
^~~
include/linux/moduleparam.h:147:2: note: in expansion of macro 'module_param_cb'
module_param_cb(name, ¶m_ops_##type, &value, perm); \
^~~~~~~~~~~~~~~
include/linux/moduleparam.h:126:2: note: in expansion of macro 'module_param_named'
module_param_named(name, name, type, perm)
^~~~~~~~~~~~~~~~~~
fs/lockd/svc.c:661:1: note: in expansion of macro 'module_param'
module_param(nsm_use_hostnames, u32, 0644);
^~~~~~~~~~~~
vim +146 include/linux/moduleparam.h
546970bc Rusty Russell 2010-08-11 140 *
546970bc Rusty Russell 2010-08-11 141 * Usually it's a good idea to have variable names and user-exposed names the
546970bc Rusty Russell 2010-08-11 142 * same, but that's harder if the variable must be non-static or is inside a
546970bc Rusty Russell 2010-08-11 143 * structure. This allows exposure under a different name.
546970bc Rusty Russell 2010-08-11 144 */
546970bc Rusty Russell 2010-08-11 145 #define module_param_named(name, value, type, perm) \
546970bc Rusty Russell 2010-08-11 @146 param_check_##type(name, &(value)); \
546970bc Rusty Russell 2010-08-11 @147 module_param_cb(name, ¶m_ops_##type, &value, perm); \
546970bc Rusty Russell 2010-08-11 148 __MODULE_PARM_TYPE(name, #type)
546970bc Rusty Russell 2010-08-11 149
546970bc Rusty Russell 2010-08-11 150 /**
:::::: The code at line 146 was first introduced by commit
:::::: 546970bc6afc7fb37447fbac09b82c7884662c21 param: add kerneldoc to moduleparam.h
:::::: TO: Rusty Russell <rusty@rustcorp.com.au>
:::::: CC: Rusty Russell <rusty@rustcorp.com.au>
---
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: 24265 bytes --]
next prev parent reply other threads:[~2016-12-12 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 15:36 [PATCH v2 0/1] " Jia He
2016-12-11 15:36 ` [PATCH v2 1/1] " Jia He
2016-12-11 17:43 ` Pan Xinhui
2016-12-11 18:03 ` Pan Xinhui
2016-12-12 2:48 ` hejianet
2016-12-12 12:54 ` kbuild test robot [this message]
2016-12-11 17:56 ` [PATCH v2 0/1] " Pan Xinhui
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=201612122048.tetBugcc%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=hejianet@gmail.com \
--cc=jlayton@poochiereds.net \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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®