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] nfsd: force_expire_client() can be static
Date: Wed, 10 Jul 2019 01:32:17 +0800 [thread overview]
Message-ID: <20190709173217.GA70574@lkp-kbuild04> (raw)
In-Reply-To: <201907100149.XLk4C7WJ%lkp@intel.com>
Fixes: 89c905beccbb ("nfsd: allow forced expiration of NFSv4 clients")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
nfs4state.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
index e6229bf..9012d78 100644
--- a/fs/nfsd/nfs4state.c
+++ b/fs/nfsd/nfs4state.c
@@ -2505,7 +2505,7 @@ static const struct file_operations client_states_fops = {
* so the caller has a guarantee that the client's locks are gone by
* the time the write returns:
*/
-void force_expire_client(struct nfs4_client *clp)
+static void force_expire_client(struct nfs4_client *clp)
{
struct nfsd_net *nn = net_generic(clp->net, nfsd_net_id);
bool already_expired;
prev parent reply other threads:[~2019-07-09 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 17:32 [linux-next:master 11868/13492] fs/nfsd/nfs4state.c:2508:6: sparse: sparse: symbol 'force_expire_client' was not declared. Should it be static? kbuild test robot
2019-07-09 17:32 ` 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=20190709173217.GA70574@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).