From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ziyang Xuan <xuanziyang2@huawei.com>
Subject: [dpdk-test-report] |WARNING| pw55439 [PATCH v6 01/15] net/hinic/base: add HW registers definition
Date: Thu, 27 Jun 2019 10:00:28 +0200 (CEST) [thread overview]
Message-ID: <20190627080028.8558A2B82@dpdk.org> (raw)
In-Reply-To: <c0cbd9b663372436657927ce35eb766233ca56e8.1561620219.git.xuanziyang2@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/55439
_coding style issues_
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'q_id' - possible side-effects?
#111: FILE: drivers/net/hinic/base/hinic_csr.h:79:
+#define HINIC_EQ_HI_PHYS_ADDR_REG(type, q_id, pg_num) \
+ ((u32)((type == HINIC_AEQ) ? \
+ HINIC_AEQ_HI_PHYS_ADDR_REG(q_id, pg_num) : \
+ HINIC_CEQ_HI_PHYS_ADDR_REG(q_id, pg_num)))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'pg_num' - possible side-effects?
#111: FILE: drivers/net/hinic/base/hinic_csr.h:79:
+#define HINIC_EQ_HI_PHYS_ADDR_REG(type, q_id, pg_num) \
+ ((u32)((type == HINIC_AEQ) ? \
+ HINIC_AEQ_HI_PHYS_ADDR_REG(q_id, pg_num) : \
+ HINIC_CEQ_HI_PHYS_ADDR_REG(q_id, pg_num)))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'q_id' - possible side-effects?
#116: FILE: drivers/net/hinic/base/hinic_csr.h:84:
+#define HINIC_EQ_LO_PHYS_ADDR_REG(type, q_id, pg_num) \
+ ((u32)((type == HINIC_AEQ) ? \
+ HINIC_AEQ_LO_PHYS_ADDR_REG(q_id, pg_num) : \
+ HINIC_CEQ_LO_PHYS_ADDR_REG(q_id, pg_num)))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'pg_num' - possible side-effects?
#116: FILE: drivers/net/hinic/base/hinic_csr.h:84:
+#define HINIC_EQ_LO_PHYS_ADDR_REG(type, q_id, pg_num) \
+ ((u32)((type == HINIC_AEQ) ? \
+ HINIC_AEQ_LO_PHYS_ADDR_REG(q_id, pg_num) : \
+ HINIC_CEQ_LO_PHYS_ADDR_REG(q_id, pg_num)))
total: 0 errors, 0 warnings, 4 checks, 160 lines checked
parent reply other threads:[~2019-06-27 8:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <c0cbd9b663372436657927ce35eb766233ca56e8.1561620219.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=20190627080028.8558A2B82@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).