From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <lkp@intel.com>
Cc: <kuniyu@amazon.com>, <linux-nfs@vger.kernel.org>,
<oe-kbuild-all@lists.linux.dev>,
<trond.myklebust@hammerspace.com>
Subject: Re: [trondmy-nfs:testing 31/31] fs/nfs/inode.c:2434:13: warning: assignment to 'int' from 'struct proc_dir_entry *' makes integer from pointer without a cast
Date: Thu, 4 Apr 2024 15:02:05 -0700 [thread overview]
Message-ID: <20240404220205.50324-1-kuniyu@amazon.com> (raw)
In-Reply-To: <202404050536.TP9zhcZf-lkp@intel.com>
From: kernel test robot <lkp@intel.com>
Date: Fri, 5 Apr 2024 05:48:13 +0800
> tree: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git testing
> head: f290a586e31f8965387dde660729c716a3af9b6c
> commit: f290a586e31f8965387dde660729c716a3af9b6c [31/31] nfs: Handle error of rpc_proc_register() in nfs_net_init().
> config: arc-defconfig (https://download.01.org/0day-ci/archive/20240405/202404050536.TP9zhcZf-lkp@intel.com/config)
> compiler: arc-elf-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240405/202404050536.TP9zhcZf-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202404050536.TP9zhcZf-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> fs/nfs/inode.c: In function 'nfs_net_init':
> >> fs/nfs/inode.c:2434:13: warning: assignment to 'int' from 'struct proc_dir_entry *' makes integer from pointer without a cast [-Wint-conversion]
> 2434 | err = rpc_proc_register(net, &nn->rpcstats);
> | ^
Ugh... sorry I forgot to turn on RPC after defconfig...
I'll post v2 soon.
Thanks!
>
>
> vim +2434 fs/nfs/inode.c
>
> 2426
> 2427 static int nfs_net_init(struct net *net)
> 2428 {
> 2429 struct nfs_net *nn = net_generic(net, nfs_net_id);
> 2430 int err;
> 2431
> 2432 nfs_clients_init(net);
> 2433
> > 2434 err = rpc_proc_register(net, &nn->rpcstats);
> 2435 if (err) {
> 2436 nfs_clients_exit(net);
> 2437 return err;
> 2438 }
> 2439
> 2440 return nfs_fs_proc_net_init(net);
> 2441 }
> 2442
>
prev parent reply other threads:[~2024-04-04 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 21:48 [trondmy-nfs:testing 31/31] fs/nfs/inode.c:2434:13: warning: assignment to 'int' from 'struct proc_dir_entry *' makes integer from pointer without a cast kernel test robot
2024-04-04 22:02 ` Kuniyuki Iwashima [this message]
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=20240404220205.50324-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=linux-nfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=trond.myklebust@hammerspace.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