From: kernel test robot <lkp@intel.com>
To: Olga Kornievskaia <kolga@netapp.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Anna Schumaker <Anna.Schumaker@Netapp.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH linux-next] nfs4_discover_trunking() can be static
Date: Wed, 12 Jan 2022 20:32:18 +0800 [thread overview]
Message-ID: <20220112123218.GA25976@65a275238185> (raw)
In-Reply-To: <202201122012.9sn7Q8EF-lkp@intel.com>
fs/nfs/nfs4proc.c:4008:5: warning: symbol 'nfs4_discover_trunking' was not declared. Should it be static?
Fixes: 82ebfb0d6333 ("NFSv4.1 query for fs_location attr on a new file system")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
nfs4proc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index a93deeca0c86f..7a59ec2d7dacc 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
@@ -4005,7 +4005,7 @@ static int _nfs4_discover_trunking(struct nfs_server *server,
return status;
}
-int nfs4_discover_trunking(struct nfs_server *server, struct nfs_fh *fhandle)
+static int nfs4_discover_trunking(struct nfs_server *server, struct nfs_fh *fhandle)
{
struct nfs4_exception exception = {
.interruptible = true,
prev parent reply other threads:[~2022-01-12 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 12:33 [linux-next:master 11662/12034] fs/nfs/nfs4proc.c:4008:5: sparse: sparse: symbol 'nfs4_discover_trunking' was not declared. Should it be static? kernel test robot
2022-01-12 12:32 ` 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=20220112123218.GA25976@65a275238185 \
--to=lkp@intel.com \
--cc=Anna.Schumaker@Netapp.com \
--cc=kbuild-all@lists.01.org \
--cc=kolga@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/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