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: [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?
Date: Mon, 4 Nov 2019 15:59:09 +0800 [thread overview]
Message-ID: <201911041524.o7kWSYSC%lkp@intel.com> (raw)
tree: git://git.samba.org/sfrench/cifs-2.6.git for-next
head: 3c652dd9928737b82a74b3ce8483c7497885eb04
commit: 4d1cc0309f7ec007b5b29f1350e3b1c105e86439 [18/20] cifs: try opening channels after mounting
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-6-g57f8611-dirty
git checkout 4d1cc0309f7ec007b5b29f1350e3b1c105e86439
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> fs/cifs/smb2transport.c:52:1: sparse: sparse: symbol 'smb3_crypto_shash_allocate' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [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?
Date: Mon, 04 Nov 2019 15:59:09 +0800 [thread overview]
Message-ID: <201911041524.o7kWSYSC%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
tree: git://git.samba.org/sfrench/cifs-2.6.git for-next
head: 3c652dd9928737b82a74b3ce8483c7497885eb04
commit: 4d1cc0309f7ec007b5b29f1350e3b1c105e86439 [18/20] cifs: try opening channels after mounting
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-6-g57f8611-dirty
git checkout 4d1cc0309f7ec007b5b29f1350e3b1c105e86439
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> fs/cifs/smb2transport.c:52:1: sparse: sparse: symbol 'smb3_crypto_shash_allocate' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2019-11-04 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 7:59 kbuild test robot [this message]
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 ` [RFC PATCH cifs] cifs: smb3_crypto_shash_allocate can be static kbuild test robot
2019-11-04 7:59 ` kbuild test robot
2019-11-05 23:00 ` Steve French
2019-11-05 23:00 ` 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=201911041524.o7kWSYSC%lkp@intel.com \
--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 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.