* [RFC PATCH linux-next] nfs4_discover_trunking() can be static
2022-01-12 12:33 [linux-next:master 11662/12034] fs/nfs/nfs4proc.c:4008:5: sparse: sparse: symbol 'nfs4_discover_trunking' was not declared. Should it be static? kernel test robot
@ 2022-01-12 12:32 ` kernel test robot
0 siblings, 0 replies; 2+ messages in thread
From: kernel test robot @ 2022-01-12 12:32 UTC (permalink / raw)
To: Olga Kornievskaia
Cc: kbuild-all, Linux Memory Management List, Anna Schumaker,
Trond Myklebust, linux-nfs, linux-kernel
fs/nfs/nfs4proc.c:4008:5: warning: symbol 'nfs4_discover_trunking' was not declared. Should it be static?
Fixes: 82ebfb0d6333 ("NFSv4.1 query for fs_location attr on a new file system")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
nfs4proc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index a93deeca0c86f..7a59ec2d7dacc 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
@@ -4005,7 +4005,7 @@ static int _nfs4_discover_trunking(struct nfs_server *server,
return status;
}
-int nfs4_discover_trunking(struct nfs_server *server, struct nfs_fh *fhandle)
+static int nfs4_discover_trunking(struct nfs_server *server, struct nfs_fh *fhandle)
{
struct nfs4_exception exception = {
.interruptible = true,
^ permalink raw reply related [flat|nested] 2+ messages in thread
* [linux-next:master 11662/12034] fs/nfs/nfs4proc.c:4008:5: sparse: sparse: symbol 'nfs4_discover_trunking' was not declared. Should it be static?
@ 2022-01-12 12:33 kernel test robot
2022-01-12 12:32 ` [RFC PATCH linux-next] nfs4_discover_trunking() can be static kernel test robot
0 siblings, 1 reply; 2+ messages in thread
From: kernel test robot @ 2022-01-12 12:33 UTC (permalink / raw)
To: Olga Kornievskaia
Cc: kbuild-all, Linux Memory Management List, Anna Schumaker,
Trond Myklebust, linux-nfs, linux-kernel
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 32ce2abb03cfae17a9eb42bd6b1b619b72f23f20
commit: 82ebfb0d633383ee00156e2b5bfa9ddf8c550b65 [11662/12034] NFSv4.1 query for fs_location attr on a new file system
config: x86_64-randconfig-s022 (https://download.01.org/0day-ci/archive/20220112/202201122012.9sn7Q8EF-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=82ebfb0d633383ee00156e2b5bfa9ddf8c550b65
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 82ebfb0d633383ee00156e2b5bfa9ddf8c550b65
# save the config file to linux build tree
mkdir build_dir
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash fs/nfs/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> fs/nfs/nfs4proc.c:4008:5: sparse: sparse: symbol 'nfs4_discover_trunking' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-01-12 12:33 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-12 12:33 [linux-next:master 11662/12034] fs/nfs/nfs4proc.c:4008:5: sparse: sparse: symbol 'nfs4_discover_trunking' was not declared. Should it be static? kernel test robot
2022-01-12 12:32 ` [RFC PATCH linux-next] nfs4_discover_trunking() can be static kernel test robot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).