From: kernel test robot <lkp@intel.com>
To: Steve French <stfrench@microsoft.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [smfrench-smb3:ksmbd-for-next-next 80/83] Warning: fs/smb/server/oplock.c:1003 function parameter 'sync' not described in 'smb2_lease_break_noti'
Date: Mon, 13 Jul 2026 11:28:05 +0800 [thread overview]
Message-ID: <202607131107.Xpl0DCti-lkp@intel.com> (raw)
tree: https://github.com/smfrench/smb3-kernel.git ksmbd-for-next-next
head: 240ab60c50a96f0b7ce00d4a299d5e1784bb5888
commit: bcd7ba0f3cba3f6d66b9fa38ecd30142bcab1b03 [80/83] ksmbd: synchronize lease breaks before renaming files
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20260713/202607131107.Xpl0DCti-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260713/202607131107.Xpl0DCti-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202607131107.Xpl0DCti-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: fs/smb/server/oplock.c:1003 function parameter 'sync' not described in 'smb2_lease_break_noti'
>> Warning: fs/smb/server/oplock.c:1003 Excess function parameter 'wait_ack' description in 'smb2_lease_break_noti'
>> Warning: fs/smb/server/oplock.c:1676 function parameter 'sync_lease_break' not described in '__smb_break_all_levII_oplock'
>> Warning: fs/smb/server/oplock.c:1003 function parameter 'sync' not described in 'smb2_lease_break_noti'
>> Warning: fs/smb/server/oplock.c:1003 Excess function parameter 'wait_ack' description in 'smb2_lease_break_noti'
>> Warning: fs/smb/server/oplock.c:1676 function parameter 'sync_lease_break' not described in '__smb_break_all_levII_oplock'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-13 3:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202607131107.Xpl0DCti-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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.