[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <201911041524.o7kWSYSC%lkp@intel.com>
Date: Mon, 4 Nov 2019 15:59:09 +0800
From: kbuild test robot <lkp@...el.com>
To: Aurelien Aptel <aaptel@...e.com>
Cc: kbuild-all@...ts.01.org, linux-cifs@...r.kernel.org,
samba-technical@...ts.samba.org,
Steve French <stfrench@...rosoft.com>,
linux-kernel@...r.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?
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@...el.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
Powered by blists - more mailing lists