From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ziyang Xuan <xuanziyang2@huawei.com>
Subject: [dpdk-test-report] |WARNING| pw54470 [PATCH v4 06/11] net/hinic/base: add code for nic business
Date: Thu, 6 Jun 2019 12:56:10 +0200 (CEST) [thread overview]
Message-ID: <20190606105610.77EAF1B9B6@dpdk.org> (raw)
In-Reply-To: <7115405f496caf5c20f8a4000b293de6c2168e75.1559818024.git.xuanziyang2@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/54470
_coding style issues_
CHECK:BOOL_MEMBER: Avoid using bool structure members because of possible alignment issues - see: https://lkml.org/lkml/2017/11/21/384
#90: FILE: drivers/net/hinic/base/hinic_pmd_nic.h:41:
+ bool registered;
CHECK:BOOL_MEMBER: Avoid using bool structure members because of possible alignment issues - see: https://lkml.org/lkml/2017/11/21/384
#91: FILE: drivers/net/hinic/base/hinic_pmd_nic.h:42:
+ bool pf_set_mac;
CHECK:BOOL_MEMBER: Avoid using bool structure members because of possible alignment issues - see: https://lkml.org/lkml/2017/11/21/384
#95: FILE: drivers/net/hinic/base/hinic_pmd_nic.h:46:
+ bool link_forced;
CHECK:BOOL_MEMBER: Avoid using bool structure members because of possible alignment issues - see: https://lkml.org/lkml/2017/11/21/384
#96: FILE: drivers/net/hinic/base/hinic_pmd_nic.h:47:
+ bool link_up; /* only valid if VF link is forced */
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'wq' - possible side-effects?
#3137: FILE: drivers/net/hinic/base/hinic_pmd_wq.h:8:
+#define WQ_WQE_ADDR(wq, idx) ((void *)((u64)((wq)->queue_buf_vaddr) + \
+ ((idx) << (wq)->wqebb_shift)))
total: 0 errors, 0 warnings, 5 checks, 3084 lines checked
parent reply other threads:[~2019-06-06 10:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <7115405f496caf5c20f8a4000b293de6c2168e75.1559818024.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=20190606105610.77EAF1B9B6@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).