From: kernel test robot <lkp@intel.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [cel:nfsd-testing 9/9] fs/nfsd/nfs4proc.c:1622:40: warning: unused variable 'nfsd4_cb_offload_ops'
Date: Thu, 25 Jul 2024 09:27:53 +0800 [thread overview]
Message-ID: <202407250956.N03o4BlA-lkp@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux nfsd-testing
head: 4e7058acdd17cdaaeedf1ace203e539dd08a2689
commit: 4e7058acdd17cdaaeedf1ace203e539dd08a2689 [9/9] NFSD: Drop CB_OFFLOAD Calls
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240725/202407250956.N03o4BlA-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/20240725/202407250956.N03o4BlA-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/202407250956.N03o4BlA-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/nfsd/nfs4proc.c:1622:40: warning: unused variable 'nfsd4_cb_offload_ops' [-Wunused-const-variable]
1622 | static const struct nfsd4_callback_ops nfsd4_cb_offload_ops = {
| ^~~~~~~~~~~~~~~~~~~~
1 warning generated.
vim +/nfsd4_cb_offload_ops +1622 fs/nfsd/nfs4proc.c
e0639dc5805a9d4 Olga Kornievskaia 2018-07-20 1621
e0639dc5805a9d4 Olga Kornievskaia 2018-07-20 @1622 static const struct nfsd4_callback_ops nfsd4_cb_offload_ops = {
e0639dc5805a9d4 Olga Kornievskaia 2018-07-20 1623 .release = nfsd4_cb_offload_release,
e0639dc5805a9d4 Olga Kornievskaia 2018-07-20 1624 .done = nfsd4_cb_offload_done
e0639dc5805a9d4 Olga Kornievskaia 2018-07-20 1625 };
e0639dc5805a9d4 Olga Kornievskaia 2018-07-20 1626
:::::: The code at line 1622 was first introduced by commit
:::::: e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 NFSD introduce async copy feature
:::::: TO: Olga Kornievskaia <kolga@netapp.com>
:::::: CC: J. Bruce Fields <bfields@redhat.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-25 1: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=202407250956.N03o4BlA-lkp@intel.com \
--to=lkp@intel.com \
--cc=chuck.lever@oracle.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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