From: kernel test robot <lkp@intel.com>
To: Xiaoming Ni <nixiaoming@huawei.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Luis Chamberlain <mcgrof@kernel.org>
Subject: [mcgrof-next:20211118-sysctl-cleanups-set-04-v2 8/36] fs/aio.c:246:62: error: macro "register_sysctl_init" passed 3 arguments, but takes just 2
Date: Fri, 19 Nov 2021 11:25:31 +0800 [thread overview]
Message-ID: <202111191128.zeN7iFma-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3081 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git 20211118-sysctl-cleanups-set-04-v2
head: 3110d41a56792588bd2f64621080948b0fceb6ab
commit: f413b2178aaff38d62d6c905d716d218388537a2 [8/36] aio: move aio sysctl to aio.c
config: nds32-allnoconfig (attached as .config)
compiler: nds32le-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git/commit/?id=f413b2178aaff38d62d6c905d716d218388537a2
git remote add mcgrof-next https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git
git fetch --no-tags mcgrof-next 20211118-sysctl-cleanups-set-04-v2
git checkout f413b2178aaff38d62d6c905d716d218388537a2
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nds32 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
fs/aio.c: In function 'aio_sysctl_init':
>> fs/aio.c:246:62: error: macro "register_sysctl_init" passed 3 arguments, but takes just 2
246 | register_sysctl_init("fs", aio_sysctls, "aio_sysctls");
| ^
In file included from include/linux/key.h:17,
from include/linux/cred.h:13,
from include/linux/sched/signal.h:10,
from include/linux/rcuwait.h:6,
from include/linux/percpu-rwsem.h:7,
from include/linux/fs.h:33,
from include/uapi/linux/aio_abi.h:31,
from fs/aio.c:18:
include/linux/sysctl.h:210: note: macro "register_sysctl_init" defined here
210 | #define register_sysctl_init(path, table) __register_sysctl_init(path, table, #table)
|
>> fs/aio.c:246:9: error: 'register_sysctl_init' undeclared (first use in this function); did you mean 'register_sysctl_paths'?
246 | register_sysctl_init("fs", aio_sysctls, "aio_sysctls");
| ^~~~~~~~~~~~~~~~~~~~
| register_sysctl_paths
fs/aio.c:246:9: note: each undeclared identifier is reported only once for each function it appears in
At top level:
fs/aio.c:226:25: warning: 'aio_sysctls' defined but not used [-Wunused-variable]
226 | static struct ctl_table aio_sysctls[] = {
| ^~~~~~~~~~~
vim +/register_sysctl_init +246 fs/aio.c
243
244 static void __init aio_sysctl_init(void)
245 {
> 246 register_sysctl_init("fs", aio_sysctls, "aio_sysctls");
247 }
248 #else
249 #define aio_sysctl_init() do { } while (0)
250 #endif
251
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 6136 bytes --]
reply other threads:[~2021-11-19 3:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202111191128.zeN7iFma-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=nixiaoming@huawei.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
Powered by JetHome