From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jlayton:dir-deleg 32/43] fs/nfsd/nfs4callback.c:900:23: warning: unused variable 'res'
Date: Thu, 22 May 2025 21:42:47 +0800 [thread overview]
Message-ID: <202505222120.oaQu7cme-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git dir-deleg
head: 0c6668479bba48114e5031d6fb3db53d80d8d6ad
commit: 118202ef11a34c160a4bb2a9bf78ddf8626b0ed3 [32/43] nfsd: add callback encoding and decoding linkages for CB_NOTIFY
config: i386-buildonly-randconfig-001-20250522 (https://download.01.org/0day-ci/archive/20250522/202505222120.oaQu7cme-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250522/202505222120.oaQu7cme-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/202505222120.oaQu7cme-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/nfsd/nfs4callback.c:900:23: warning: unused variable 'res' [-Wunused-variable]
900 | struct CB_NOTIFY4res res;
| ^~~
1 warning generated.
vim +/res +900 fs/nfsd/nfs4callback.c
893
894 static int nfs4_xdr_dec_cb_notify(struct rpc_rqst *rqstp,
895 struct xdr_stream *xdr,
896 void *data)
897 {
898 struct nfsd4_callback *cb = data;
899 struct nfs4_cb_compound_hdr hdr;
> 900 struct CB_NOTIFY4res res;
901 int status;
902
903 status = decode_cb_compound4res(xdr, &hdr);
904 if (unlikely(status))
905 return status;
906
907 status = decode_cb_sequence4res(xdr, cb);
908 if (unlikely(status || cb->cb_seq_status))
909 return status;
910
911 return decode_cb_op_status(xdr, OP_CB_NOTIFY, &cb->cb_status);
912 }
913
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-22 13:42 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=202505222120.oaQu7cme-lkp@intel.com \
--to=lkp@intel.com \
--cc=jlayton@kernel.org \
--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