From: kernel test robot <lkp@intel.com>
To: Benjamin Coddington <bcodding@redhat.com>, linux-nfs@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Anna.Schumaker@netapp.com,
Olga.Kornievskaia@netapp.com
Subject: Re: [PATCH 2/6] NFS: rename nfs_client_kobj to nfs_net_kobj
Date: Fri, 7 Apr 2023 06:48:59 +0800 [thread overview]
Message-ID: <202304070607.zNXFIg0W-lkp@intel.com> (raw)
In-Reply-To: <75aec6f877a89c63478073861cf277bbfcb90453.1680786859.git.bcodding@redhat.com>
Hi Benjamin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on trondmy-nfs/linux-next]
[also build test WARNING on linus/master v6.3-rc5 next-20230406]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Benjamin-Coddington/NFS-rename-nfs_client_kset-to-nfs_kset/20230406-221247
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
patch link: https://lore.kernel.org/r/75aec6f877a89c63478073861cf277bbfcb90453.1680786859.git.bcodding%40redhat.com
patch subject: [PATCH 2/6] NFS: rename nfs_client_kobj to nfs_net_kobj
config: i386-randconfig-s001-20230403 (https://download.01.org/0day-ci/archive/20230407/202304070607.zNXFIg0W-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://github.com/intel-lab-lkp/linux/commit/27e42c94f90782f5d27b8de8e18d701e99764a03
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Benjamin-Coddington/NFS-rename-nfs_client_kset-to-nfs_kset/20230406-221247
git checkout 27e42c94f90782f5d27b8de8e18d701e99764a03
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 olddefconfig
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash fs/nfs/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304070607.zNXFIg0W-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/nfs/sysfs.c:20:16: sparse: sparse: symbol 'nfs_net_kobj' was not declared. Should it be static?
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-04-06 22:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 14:09 [PATCH 0/6] RFC: NFS sysfs mounts to rpc client structure Benjamin Coddington
2023-04-06 14:09 ` [PATCH 1/6] NFS: rename nfs_client_kset to nfs_kset Benjamin Coddington
2023-04-06 14:10 ` [PATCH 2/6] NFS: rename nfs_client_kobj to nfs_net_kobj Benjamin Coddington
2023-04-06 22:48 ` kernel test robot [this message]
2023-04-06 14:10 ` [PATCH 3/6] NFS: add superblock sysfs entries Benjamin Coddington
2023-04-06 16:38 ` kernel test robot
2023-04-06 16:38 ` kernel test robot
2023-04-06 14:10 ` [PATCH 4/6] NFS: Add sysfs links to sunrpc clients for nfs_clients Benjamin Coddington
2023-04-06 14:10 ` [PATCH 5/6] NFS: add a sysfs link to the lockd rpc_client Benjamin Coddington
2023-04-06 14:10 ` [PATCH 6/6] NFS: add a sysfs link to the acl rpc_client Benjamin Coddington
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=202304070607.zNXFIg0W-lkp@intel.com \
--to=lkp@intel.com \
--cc=Anna.Schumaker@netapp.com \
--cc=Olga.Kornievskaia@netapp.com \
--cc=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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