automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ziyang Xuan <xuanziyang2@huawei.com>
Subject: [dpdk-test-report] |WARNING| pw54477 [PATCH v4 04/11] net/hinic/base: add code about hardware operation
Date: Thu,  6 Jun 2019 13:04:51 +0200 (CEST)	[thread overview]
Message-ID: <20190606110451.759B81B9A6@dpdk.org> (raw)
In-Reply-To: <4f346071d6d54fd81bf90dc54d4782ec6d0d5cbd.1559818024.git.xuanziyang2@huawei.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/54477

_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
#349: FILE: drivers/net/hinic/base/hinic_pmd_cfg.h:28:
+	bool ft_en;     /* business enable flag (not include RDMA) */

CHECK:BOOL_MEMBER: Avoid using bool structure members because of possible alignment issues - see: https://lkml.org/lkml/2017/11/21/384
#350: FILE: drivers/net/hinic/base/hinic_pmd_cfg.h:29:
+	bool ft_pf_en;  /* In FPGA Test VF resource is in PF or not,

CHECK:BOOL_MEMBER: Avoid using bool structure members because of possible alignment issues - see: https://lkml.org/lkml/2017/11/21/384
#354: FILE: drivers/net/hinic/base/hinic_pmd_cfg.h:33:
+	bool rdma_en;

CHECK:BOOL_MEMBER: Avoid using bool structure members because of possible alignment issues - see: https://lkml.org/lkml/2017/11/21/384
#355: FILE: drivers/net/hinic/base/hinic_pmd_cfg.h:34:
+	bool rdma_pf_en; /* In FPGA Test VF RDMA resource is in PF or not,

CHECK:BOOL_MEMBER: Avoid using bool structure members because of possible alignment issues - see: https://lkml.org/lkml/2017/11/21/384
#379: FILE: drivers/net/hinic/base/hinic_pmd_cfg.h:58:
+	bool sf_en;	/* stateful business status */

total: 0 errors, 0 warnings, 5 checks, 2963 lines checked

           reply	other threads:[~2019-06-06 11:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4f346071d6d54fd81bf90dc54d4782ec6d0d5cbd.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=20190606110451.759B81B9A6@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).