From: kbuild test robot <lkp@intel.com>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: kbuild-all@01.org, Jeff Layton <jlayton@kernel.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH linux-next] nfsd4: __get_nfsdfs_client() can be static
Date: Tue, 9 Jul 2019 21:55:44 +0800 [thread overview]
Message-ID: <20190709135544.GA4675@lkp-kbuild04> (raw)
In-Reply-To: <201907092159.SKYltvLT%lkp@intel.com>
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;
prev parent reply other threads:[~2019-07-09 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [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=20190709135544.GA4675@lkp-kbuild04 \
--to=lkp@intel.com \
--cc=bfields@redhat.com \
--cc=jlayton@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).