From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH jlayton] ceph: ceph_netfs_read_ops can be static
Date: Thu, 18 Feb 2021 10:25:42 +0800 [thread overview]
Message-ID: <20210218022541.GA4862@afca28aacbfc> (raw)
In-Reply-To: <202102181050.yd2AfPof-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
Fixes: a4c56bdbfcd4 ("ceph: convert readpage to fscache read helper")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
addr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ceph/addr.c b/fs/ceph/addr.c
index 81146d75f85e5..0a73121341efb 100644
--- a/fs/ceph/addr.c
+++ b/fs/ceph/addr.c
@@ -301,7 +301,7 @@ static void ceph_init_rreq(struct netfs_read_request *rreq, struct file *file)
{
}
-const struct netfs_read_request_ops ceph_netfs_read_ops = {
+static const struct netfs_read_request_ops ceph_netfs_read_ops = {
.init_rreq = ceph_init_rreq,
.is_cache_enabled = ceph_is_cache_enabled,
.begin_cache_operation = ceph_begin_cache_operation,
prev parent reply other threads:[~2021-02-18 2:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 2:25 [jlayton:ceph-netfs-lib 4/6] fs/ceph/addr.c:304:37: sparse: sparse: symbol 'ceph_netfs_read_ops' was not declared. Should it be kernel test robot
2021-02-18 2:25 ` kernel 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=20210218022541.GA4862@afca28aacbfc \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.