From: kernel test robot <lkp@intel.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Steve French <stfrench@microsoft.com>
Subject: [samba-ksmbd:ksmbd-for-next-next 4/4] fs/smb/server/vfs_cache.c:39:27: warning: unused variable 'dh_task'
Date: Mon, 15 Jul 2024 03:45:29 +0800 [thread overview]
Message-ID: <202407150316.TZgyiAbN-lkp@intel.com> (raw)
tree: git://git.samba.org/ksmbd.git ksmbd-for-next-next
head: c11a5805413bdbe0a22e94458aeeda3bac9b63a7
commit: c11a5805413bdbe0a22e94458aeeda3bac9b63a7 [4/4] ksmbd: add durable scavenger timer
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20240715/202407150316.TZgyiAbN-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240715/202407150316.TZgyiAbN-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/202407150316.TZgyiAbN-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/smb/server/vfs_cache.c:39:27: warning: unused variable 'dh_task' [-Wunused-variable]
39 | static struct task_struc *dh_task;
| ^~~~~~~
1 warning generated.
vim +/dh_task +39 fs/smb/server/vfs_cache.c
36
37 static bool durable_scavenger_running;
38 static DEFINE_MUTEX(durable_scavenger_lock);
> 39 static struct task_struc *dh_task;
40 static wait_queue_head_t dh_wq;
41
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-14 19:46 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=202407150316.TZgyiAbN-lkp@intel.com \
--to=lkp@intel.com \
--cc=linkinjeon@kernel.org \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox