From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Haiyue Wang <haiyue.wang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw85131 [PATCH v2 1/5] common/iavf: new VLAN opcode
Date: Mon, 14 Dec 2020 08:28:34 +0100 (CET) [thread overview]
Message-ID: <20201214072834.D8F93C97C@dpdk.org> (raw)
In-Reply-To: <20201214071155.98764-2-haiyue.wang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/85131
_coding style issues_
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#117: FILE: drivers/common/iavf/virtchnl.h:561:
+ * ^IVIRTHCNL_VLAN_ETHERTYPE_8100 |$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#118: FILE: drivers/common/iavf/virtchnl.h:562:
+ * ^IVIRTCHNL_VLAN_ETHERTYPE_88A8 |$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#119: FILE: drivers/common/iavf/virtchnl.h:563:
+ * ^IVIRTCHNL_VLAN_ETHERTYPE_AND;$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#130: FILE: drivers/common/iavf/virtchnl.h:574:
+ * ^IVIRTCHNL_VLAN_ETHERTYPE_8100 |$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#131: FILE: drivers/common/iavf/virtchnl.h:575:
+ * ^IVIRTCHNL_VLAN_ETHERTYPE_88A8 |$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#132: FILE: drivers/common/iavf/virtchnl.h:576:
+ * ^IVIRTCHNL_VLAN_ETHERTYPE_XOR;$
WARNING:TYPO_SPELLING: 'sepcified' may be misspelled - perhaps 'specified'?
#184: FILE: drivers/common/iavf/virtchnl.h:628:
+ * for stripping affect the ethertype(s) sepcified for insertion and visa versa
WARNING:TYPO_SPELLING: 'stipped' may be misspelled - perhaps 'stripped'?
#206: FILE: drivers/common/iavf/virtchnl.h:650:
+ * The VF driver needs to be aware of how the tags are stipped by hardware and
WARNING:LONG_LINE_COMMENT: line length of 107 exceeds 100 columns
#291: FILE: drivers/common/iavf/virtchnl.h:735:
+ u16 outer_ethertype_setting; /* 0x8100, 0x88a8, etc. and only type(s) set in the offload caps */
WARNING:LONG_LINE_COMMENT: line length of 107 exceeds 100 columns
#292: FILE: drivers/common/iavf/virtchnl.h:736:
+ u16 inner_ethertype_setting; /* 0x8100, 0x88a8, etc. and only type(s) set in the offload caps */
total: 0 errors, 10 warnings, 259 lines checked
parent reply other threads:[~2020-12-14 7:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201214071155.98764-2-haiyue.wang@intel.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=20201214072834.D8F93C97C@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=test-report@dpdk.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 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).