From: kernel test robot <lkp@intel.com>
To: Dust Li <dust.li@linux.alibaba.com>,
Karsten Graul <kgraul@linux.ibm.com>,
Tony Lu <tonylu@linux.alibaba.com>,
davem@davemloft.net, kuba@kernel.org
Cc: kbuild-all@lists.01.org, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next] net/smc: fix compile warning for smc_sysctl
Date: Wed, 2 Mar 2022 23:02:23 +0800 [thread overview]
Message-ID: <202203022234.AMB3WcyJ-lkp@intel.com> (raw)
In-Reply-To: <20220302034312.31168-1-dust.li@linux.alibaba.com>
Hi Dust,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Dust-Li/net-smc-fix-compile-warning-for-smc_sysctl/20220302-114411
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 7282c126f7688f697d33f3b965c29bba67fb4eba
config: sparc-buildonly-randconfig-r005-20220302 (https://download.01.org/0day-ci/archive/20220302/202203022234.AMB3WcyJ-lkp@intel.com/config)
compiler: sparc64-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://github.com/0day-ci/linux/commit/4b16b08f4709ad49412ee1df69b6922a370dad46
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Dust-Li/net-smc-fix-compile-warning-for-smc_sysctl/20220302-114411
git checkout 4b16b08f4709ad49412ee1df69b6922a370dad46
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=sparc SHELL=/bin/bash net/smc/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
net/smc/smc_sysctl.c: In function 'smc_sysctl_init_net':
net/smc/smc_sysctl.c:47:17: error: 'struct netns_smc' has no member named 'smc_hdr'
47 | net->smc.smc_hdr = register_net_sysctl(net, "net/smc", table);
| ^
net/smc/smc_sysctl.c:48:22: error: 'struct netns_smc' has no member named 'smc_hdr'
48 | if (!net->smc.smc_hdr)
| ^
net/smc/smc_sysctl.c: In function 'smc_sysctl_exit_net':
net/smc/smc_sysctl.c:64:45: error: 'struct netns_smc' has no member named 'smc_hdr'
64 | unregister_net_sysctl_table(net->smc.smc_hdr);
| ^
net/smc/smc_sysctl.c: At top level:
net/smc/smc_sysctl.c:72:16: error: redefinition of 'smc_sysctl_init'
72 | int __net_init smc_sysctl_init(void)
| ^~~~~~~~~~~~~~~
In file included from net/smc/smc_sysctl.c:18:
net/smc/smc_sysctl.h:23:19: note: previous definition of 'smc_sysctl_init' with type 'int(void)'
23 | static inline int smc_sysctl_init(void)
| ^~~~~~~~~~~~~~~
>> net/smc/smc_sysctl.c:78:1: warning: ignoring attribute 'noinline' because it conflicts with attribute 'gnu_inline' [-Wattributes]
78 | {
| ^
In file included from net/smc/smc_sysctl.c:18:
net/smc/smc_sysctl.h:28:20: note: previous declaration here
28 | static inline void smc_sysctl_exit(void) { }
| ^~~~~~~~~~~~~~~
net/smc/smc_sysctl.c:77:17: error: redefinition of 'smc_sysctl_exit'
77 | void __net_exit smc_sysctl_exit(void)
| ^~~~~~~~~~~~~~~
In file included from net/smc/smc_sysctl.c:18:
net/smc/smc_sysctl.h:28:20: note: previous definition of 'smc_sysctl_exit' with type 'void(void)'
28 | static inline void smc_sysctl_exit(void) { }
| ^~~~~~~~~~~~~~~
vim +78 net/smc/smc_sysctl.c
462791bbfa35018 Dust Li 2022-03-01 76
4b16b08f4709ad4 Dust Li 2022-03-02 77 void __net_exit smc_sysctl_exit(void)
462791bbfa35018 Dust Li 2022-03-01 @78 {
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2022-03-02 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 3:43 [PATCH net-next] net/smc: fix compile warning for smc_sysctl Dust Li
2022-03-02 5:49 ` Tony Lu
2022-03-02 15:02 ` kernel test robot [this message]
2022-03-02 19:45 ` Jakub Kicinski
2022-03-02 19:45 ` Jakub Kicinski
2022-03-03 2:35 ` dust.li
2022-03-03 2:35 ` dust.li
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=202203022234.AMB3WcyJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=kbuild-all@lists.01.org \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tonylu@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.