From: kbuild test robot <fengguang.wu@intel.com>
To: Long Li <longli@microsoft.com>
Cc: kbuild-all@01.org, Steve French <smfrench@gmail.com>,
Pavel Shilovsky <pshilov@microsoft.com>,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH linux-next] CIFS: SMBD: _smbd_get_connection() can be static
Date: Mon, 18 Dec 2017 21:30:06 +0800 [thread overview]
Message-ID: <20171218133006.GA79761@cairo> (raw)
In-Reply-To: <201712182136.tWBuroDL%fengguang.wu@intel.com>
Fixes: 07495ff5d9bc ("CIFS: SMBD: Establish SMB Direct connection")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
smbdirect.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/cifs/smbdirect.c b/fs/cifs/smbdirect.c
index 2ecd5c1..62a5c3f 100644
--- a/fs/cifs/smbdirect.c
+++ b/fs/cifs/smbdirect.c
@@ -1462,7 +1462,7 @@ static int allocate_caches_and_workqueue(struct smbd_connection *info)
}
/* Create a SMBD connection, called by upper layer */
-struct smbd_connection *_smbd_get_connection(
+static struct smbd_connection *_smbd_get_connection(
struct TCP_Server_Info *server, struct sockaddr *dstaddr, int port)
{
int rc;
next prev parent reply other threads:[~2017-12-18 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 13:30 [linux-next:master 5061/5571] fs/cifs/smbdirect.c:1465:24: sparse: symbol '_smbd_get_connection' was not declared. Should it be static? kbuild test robot
2017-12-18 13:30 ` kbuild test robot [this message]
2017-12-18 21:44 ` [RFC PATCH linux-next] CIFS: SMBD: _smbd_get_connection() can be static Long Li
2018-01-03 23:15 ` Steve French
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=20171218133006.GA79761@cairo \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=pshilov@microsoft.com \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.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