From: kernel test robot <lkp@intel.com>
To: Sasha Levin <sashal@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [sashal-stable:pending-6.4 111/141] drivers/infiniband/hw/bnxt_re/qplib_rcfw.c:71:6: warning: variable 'ret' set but not used
Date: Mon, 31 Jul 2023 10:06:35 +0800 [thread overview]
Message-ID: <202307310925.KyE2S5zu-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git pending-6.4
head: ade14a1785368ef634f78e4a46ce217f7937b066
commit: 4e26ad911226b36d88aa2bd48a39917a276afdfa [111/141] RDMA/bnxt_re: Enhance the existing functions that wait for FW responses
config: x86_64-randconfig-r011-20230731 (https://download.01.org/0day-ci/archive/20230731/202307310925.KyE2S5zu-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce: (https://download.01.org/0day-ci/archive/20230731/202307310925.KyE2S5zu-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/202307310925.KyE2S5zu-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/infiniband/hw/bnxt_re/qplib_rcfw.c:71:6: warning: variable 'ret' set but not used [-Wunused-but-set-variable]
int ret;
^
1 warning generated.
vim +/ret +71 drivers/infiniband/hw/bnxt_re/qplib_rcfw.c
55
56 /**
57 * __wait_for_resp - Don't hold the cpu context and wait for response
58 * @rcfw - rcfw channel instance of rdev
59 * @cookie - cookie to track the command
60 *
61 * Wait for command completion in sleepable context.
62 *
63 * Returns:
64 * 0 if command is completed by firmware.
65 * Non zero error code for rest of the case.
66 */
67 static int __wait_for_resp(struct bnxt_qplib_rcfw *rcfw, u16 cookie)
68 {
69 struct bnxt_qplib_cmdq_ctx *cmdq;
70 u16 cbit;
> 71 int ret;
72
73 cmdq = &rcfw->cmdq;
74 cbit = cookie % rcfw->cmdq_depth;
75
76 do {
77 /* Non zero means command completed */
78 ret = wait_event_timeout(cmdq->waitq,
79 !test_bit(cbit, cmdq->cmdq_bitmap),
80 msecs_to_jiffies(10000));
81
82 if (!test_bit(cbit, cmdq->cmdq_bitmap))
83 return 0;
84
85 bnxt_qplib_service_creq(&rcfw->creq.creq_tasklet);
86
87 if (!test_bit(cbit, cmdq->cmdq_bitmap))
88 return 0;
89
90 } while (true);
91 };
92
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-31 2:06 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=202307310925.KyE2S5zu-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sashal@kernel.org \
/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.