From: kernel test robot <lkp@intel.com>
To: Shyam Prasad N <sprasad@microsoft.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 41/41] fs/cifs/smb2ops.c:2671:1: sparse: sparse: symbol 'smb2_query_info_compound_final' was not declared. Should it be static?
Date: Wed, 28 Apr 2021 11:37:12 +0800 [thread overview]
Message-ID: <202104281139.5F0W4c8s-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3244 bytes --]
tree: git://git.samba.org/sfrench/cifs-2.6.git for-next
head: 20b184c6741b0e1d4ab569e87ec36b2c23b2298d
commit: 20b184c6741b0e1d4ab569e87ec36b2c23b2298d [41/41] cifs: when out of credits on one channel, retry on another.
config: x86_64-randconfig-s022-20210428 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
git remote add cifs git://git.samba.org/sfrench/cifs-2.6.git
git fetch --no-tags cifs for-next
git checkout 20b184c6741b0e1d4ab569e87ec36b2c23b2298d
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> fs/cifs/smb2ops.c:2671:1: sparse: sparse: symbol 'smb2_query_info_compound_final' was not declared. Should it be static?
>> fs/cifs/smb2ops.c:3284:1: sparse: sparse: symbol 'smb2_query_reparse_tag_final' was not declared. Should it be static?
--
>> fs/cifs/smb2pdu.c:2478:5: sparse: sparse: symbol 'smb311_posix_mkdir_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:2842:1: sparse: sparse: symbol 'SMB2_open_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:3056:1: sparse: sparse: symbol 'SMB2_ioctl_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:3247:1: sparse: sparse: symbol '__SMB2_close_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:3641:1: sparse: sparse: symbol 'SMB2_change_notify_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:3870:1: sparse: sparse: symbol 'SMB2_flush_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:4118:1: sparse: sparse: symbol 'smb2_async_readv_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:4205:1: sparse: sparse: symbol 'SMB2_read_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:4388:1: sparse: sparse: symbol 'smb2_async_writev_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:4542:1: sparse: sparse: symbol 'SMB2_write_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:4946:1: sparse: sparse: symbol 'SMB2_query_directory_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:5200:1: sparse: sparse: symbol 'SMB2_oplock_break_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:5333:1: sparse: sparse: symbol 'SMB311_posix_qfs_info_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:5398:1: sparse: sparse: symbol 'SMB2_QFS_info_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:5463:1: sparse: sparse: symbol 'SMB2_QFS_attr_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:5562:1: sparse: sparse: symbol 'smb2_lockv_final' was not declared. Should it be static?
>> fs/cifs/smb2pdu.c:5654:1: sparse: sparse: symbol 'SMB2_lease_break_final' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31576 bytes --]
next reply other threads:[~2021-04-28 3:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 3:37 kernel test robot [this message]
2021-04-28 3:37 ` [RFC PATCH cifs] cifs: smb2_query_info_compound_final can be static kernel test robot
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=202104281139.5F0W4c8s-lkp@intel.com \
--to=lkp@intel.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=sprasad@microsoft.com \
--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