From: kbuild test robot <lkp@intel.com>
To: Aurelien Aptel <aaptel@suse.com>
Cc: kbuild-all@lists.01.org, linux-cifs@vger.kernel.org,
samba-technical@lists.samba.org,
Steve French <stfrench@microsoft.com>,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH cifs] cifs: smb3_crypto_shash_allocate can be static
Date: Mon, 4 Nov 2019 15:59:11 +0800 [thread overview]
Message-ID: <20191104075911.23rhzcbztbhlbjk5@4978f4969bb8> (raw)
In-Reply-To: <201911041524.o7kWSYSC%lkp@intel.com>
Fixes: 4d1cc0309f7e ("cifs: try opening channels after mounting")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
smb2transport.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/cifs/smb2transport.c b/fs/cifs/smb2transport.c
index 1af789871ec2e..86501239cef55 100644
--- a/fs/cifs/smb2transport.c
+++ b/fs/cifs/smb2transport.c
@@ -48,7 +48,7 @@ smb2_crypto_shash_allocate(struct TCP_Server_Info *server)
&server->secmech.sdeschmacsha256);
}
-int
+static int
smb3_crypto_shash_allocate(struct TCP_Server_Info *server)
{
struct cifs_secmech *p = &server->secmech;
next prev parent reply other threads:[~2019-11-04 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 7:59 [cifs:for-next 18/20] fs/cifs/smb2transport.c:52:1: sparse: sparse: symbol 'smb3_crypto_shash_allocate' was not declared. Should it be static? kbuild test robot
2019-11-04 7:59 ` kbuild test robot [this message]
2019-11-05 23:00 ` [RFC PATCH cifs] cifs: smb3_crypto_shash_allocate can be static 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=20191104075911.23rhzcbztbhlbjk5@4978f4969bb8 \
--to=lkp@intel.com \
--cc=aaptel@suse.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=stfrench@microsoft.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;
as well as URLs for NNTP newsgroup(s).