From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ziyang Xuan <xuanziyang2@huawei.com>
Subject: [dpdk-test-report] |WARNING| pw55074 [PATCH v5 13/15] net/hinic: add start stop close queue ops
Date: Thu, 20 Jun 2019 11:54:02 +0200 (CEST) [thread overview]
Message-ID: <20190620095402.39E6C1D0CA@dpdk.org> (raw)
In-Reply-To: <080a5b324a9f3d9e4036cf4b74cda39a16d47a31.1560958308.git.xuanziyang2@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/55074
_coding style issues_
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'rxq' - possible side-effects?
#784: FILE: drivers/net/hinic/hinic_pmd_rx.c:20:
+#define HINIC_GET_RQ_LOCAL_CI(rxq) \
+ (((rxq)->wq->cons_idx) & HINIC_GET_RQ_WQE_MASK(rxq))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'rxq' - possible side-effects?
#787: FILE: drivers/net/hinic/hinic_pmd_rx.c:23:
+#define HINIC_GET_RQ_LOCAL_PI(rxq) \
+ (((rxq)->wq->prod_idx) & HINIC_GET_RQ_WQE_MASK(rxq))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'rxq' - possible side-effects?
#790: FILE: drivers/net/hinic/hinic_pmd_rx.c:26:
+#define HINIC_UPDATE_RQ_LOCAL_CI(rxq, wqebb_cnt) \
+ do { \
+ (rxq)->wq->cons_idx += (wqebb_cnt); \
+ (rxq)->wq->delta += (wqebb_cnt); \
+ } while (0)
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'wqebb_cnt' - possible side-effects?
#790: FILE: drivers/net/hinic/hinic_pmd_rx.c:26:
+#define HINIC_UPDATE_RQ_LOCAL_CI(rxq, wqebb_cnt) \
+ do { \
+ (rxq)->wq->cons_idx += (wqebb_cnt); \
+ (rxq)->wq->delta += (wqebb_cnt); \
+ } while (0)
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'rxq' - possible side-effects?
#796: FILE: drivers/net/hinic/hinic_pmd_rx.c:32:
+#define HINIC_UPDATE_RQ_HW_PI(rxq, pi) \
+ (*((rxq)->pi_virt_addr) = \
+ cpu_to_be16((pi) & HINIC_GET_RQ_WQE_MASK(rxq)))
total: 0 errors, 0 warnings, 5 checks, 1265 lines checked
parent reply other threads:[~2019-06-20 9:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <080a5b324a9f3d9e4036cf4b74cda39a16d47a31.1560958308.git.xuanziyang2@huawei.com>]
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=20190620095402.39E6C1D0CA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=xuanziyang2@huawei.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;
as well as URLs for NNTP newsgroup(s).