From: kernel test robot <lkp@intel.com>
To: Dai Ngo <dai.ngo@oracle.com>, bfields@fieldses.org
Cc: kbuild-all@lists.01.org, linux-nfs@vger.kernel.org
Subject: [RFC PATCH] NFSv4.2: nfs_ssc_clnt_ops_tbl can be static
Date: Thu, 8 Oct 2020 11:11:26 +0800 [thread overview]
Message-ID: <20201008031126.GA156798@30b510b0eab4> (raw)
In-Reply-To: <20201008012513.89989-2-dai.ngo@oracle.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
nfs4file.c | 2 +-
super.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/nfs/nfs4file.c b/fs/nfs/nfs4file.c
index ea42c39bc2ffd..124876dfd6447 100644
--- a/fs/nfs/nfs4file.c
+++ b/fs/nfs/nfs4file.c
@@ -28,7 +28,7 @@ static struct file *__nfs42_ssc_open(struct vfsmount *ss_mnt,
struct nfs_fh *src_fh, nfs4_stateid *stateid);
static void __nfs42_ssc_close(struct file *filep);
-const struct nfs4_ssc_client_ops nfs4_ssc_clnt_ops_tbl = {
+static const struct nfs4_ssc_client_ops nfs4_ssc_clnt_ops_tbl = {
.sco_owner = THIS_MODULE,
.sco_open = __nfs42_ssc_open,
.sco_close = __nfs42_ssc_close,
diff --git a/fs/nfs/super.c b/fs/nfs/super.c
index c6324e2de1ae5..65636fef6a006 100644
--- a/fs/nfs/super.c
+++ b/fs/nfs/super.c
@@ -86,7 +86,7 @@ const struct super_operations nfs_sops = {
};
EXPORT_SYMBOL_GPL(nfs_sops);
-const struct nfs_ssc_client_ops nfs_ssc_clnt_ops_tbl = {
+static const struct nfs_ssc_client_ops nfs_ssc_clnt_ops_tbl = {
.sco_owner = THIS_MODULE,
.sco_sb_deactive = nfs_sb_deactive,
};
next prev parent reply other threads:[~2020-10-08 3:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 1:25 [PATCH v2 0/1] NFSv4.2: Fix NFS4ERR_STALE with inter server copy Dai Ngo
2020-10-08 1:25 ` [PATCH v2 1/1] NFSv4.2: Fix NFS4ERR_STALE error when doing " Dai Ngo
2020-10-08 2:56 ` kernel test robot
2020-10-08 3:11 ` kernel test robot
2020-10-08 3:11 ` kernel test robot [this message]
2020-10-08 3:24 ` kernel test robot
2020-10-08 17:58 ` [PATCH v2 0/1] NFSv4.2: Fix NFS4ERR_STALE with " J. Bruce Fields
2020-10-08 18:29 ` Dai Ngo
2020-10-08 19:47 ` J. Bruce Fields
2020-10-08 21:15 ` Dai Ngo
2020-10-08 21:17 ` Dai Ngo
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=20201008031126.GA156798@30b510b0eab4 \
--to=lkp@intel.com \
--cc=bfields@fieldses.org \
--cc=dai.ngo@oracle.com \
--cc=kbuild-all@lists.01.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).