linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [linux-next:master 11860/13492] fs/nfsd/nfsctl.c:1221:22: sparse: sparse: symbol '__get_nfsdfs_client' was not declared. Should it be static?
@ 2019-07-09 13:55 kbuild test robot
  2019-07-09 13:55 ` [RFC PATCH linux-next] nfsd4: __get_nfsdfs_client() can be static kbuild test robot
  0 siblings, 1 reply; 2+ messages in thread
From: kbuild test robot @ 2019-07-09 13:55 UTC (permalink / raw)
  To: J. Bruce Fields; +Cc: kbuild-all, Jeff Layton, linux-nfs, linux-kernel

tree:   https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git master
head:   4608a726c66807c27bc7d91bdf8a288254e29985
commit: 97ad4031e29521894fc28765f14247e79b0ef263 [11860/13492] nfsd4: add a client info file
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-rc1-7-g2b96cd8-dirty
        git checkout 97ad4031e29521894fc28765f14247e79b0ef263
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

>> fs/nfsd/nfsctl.c:1221:22: sparse: sparse: symbol '__get_nfsdfs_client' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [RFC PATCH linux-next] nfsd4: __get_nfsdfs_client() can be static
  2019-07-09 13:55 [linux-next:master 11860/13492] fs/nfsd/nfsctl.c:1221:22: sparse: sparse: symbol '__get_nfsdfs_client' was not declared. Should it be static? kbuild test robot
@ 2019-07-09 13:55 ` kbuild test robot
  0 siblings, 0 replies; 2+ messages in thread
From: kbuild test robot @ 2019-07-09 13:55 UTC (permalink / raw)
  To: J. Bruce Fields; +Cc: kbuild-all, Jeff Layton, linux-nfs, linux-kernel


Fixes: 97ad4031e295 ("nfsd4: add a client info file")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
 nfsctl.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd/nfsctl.c
index 4683ba5..72fad54 100644
--- a/fs/nfsd/nfsctl.c
+++ b/fs/nfsd/nfsctl.c
@@ -1218,7 +1218,7 @@ static void clear_ncl(struct inode *inode)
 }
 
 
-struct nfsdfs_client *__get_nfsdfs_client(struct inode *inode)
+static struct nfsdfs_client *__get_nfsdfs_client(struct inode *inode)
 {
 	struct nfsdfs_client *nc = inode->i_private;
 

^ permalink raw reply related	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-07-09 13:56 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-09 13:55 [linux-next:master 11860/13492] fs/nfsd/nfsctl.c:1221:22: sparse: sparse: symbol '__get_nfsdfs_client' was not declared. Should it be static? kbuild test robot
2019-07-09 13:55 ` [RFC PATCH linux-next] nfsd4: __get_nfsdfs_client() can be static kbuild 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).