From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: [dpdk-test-report] |WARNING| pw25076 [PATCH] dpdk: remove typos using codespell utility
Date: Wed, 7 Jun 2017 07:06:56 +0200 (CEST) [thread overview]
Message-ID: <20170607050656.39DD82BB8@dpdk.org> (raw)
In-Reply-To: <20170607050506.31012-1-jerin.jacob@caviumnetworks.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/25076
_coding style issues_
WARNING:LONG_LINE: line over 90 characters
#421: FILE: drivers/net/bnx2x/ecore_hsi.h:3914:
+ uint16_t rx_cos_mask /* the bits that will be set on pfc/ safc paket with will be genratet when this ring is full. for regular flow control set this to 1 */;
WARNING:LONG_LINE_COMMENT: line over 90 characters
#439: FILE: drivers/net/bnx2x/ecore_hsi.h:4940:
+#define MAC_CONFIGURATION_ENTRY_OVERRIDE_VLAN_REMOVAL (0x1<<4) /* BitField flags BitField flags 0 - can't remove vlan 1 - can remove vlan. relevant only to everest1 */
CHECK:SPACING: spaces preferred around that '<<' (ctx:VxV)
#439: FILE: drivers/net/bnx2x/ecore_hsi.h:4940:
+#define MAC_CONFIGURATION_ENTRY_OVERRIDE_VLAN_REMOVAL (0x1<<4) /* BitField flags BitField flags 0 - can't remove vlan 1 - can remove vlan. relevant only to everest1 */
^
WARNING:LONG_LINE_COMMENT: line over 90 characters
#448: FILE: drivers/net/bnx2x/ecore_hsi.h:5027:
+#define TSTORM_ETH_FUNCTION_COMMON_CONFIG_VLAN_FILTERING_ENABLE (0x1<<7) /* BitField config_flagsGeneral configuration flags 0 - Don't filter by vlan, 1 - Filter according to the vlans specificied in mac_filter_config */
CHECK:SPACING: spaces preferred around that '<<' (ctx:VxV)
#448: FILE: drivers/net/bnx2x/ecore_hsi.h:5027:
+#define TSTORM_ETH_FUNCTION_COMMON_CONFIG_VLAN_FILTERING_ENABLE (0x1<<7) /* BitField config_flagsGeneral configuration flags 0 - Don't filter by vlan, 1 - Filter according to the vlans specificied in mac_filter_config */
^
WARNING:LONG_LINE: line over 90 characters
#457: FILE: drivers/net/bnx2x/ecore_hsi.h:5637:
+ uint8_t allow_npar_tx_switching /* If set, inter-pf tx switching is allowed in Switch Independent function mode. (E2/E3 Only) */;
WARNING:LONG_LINE_COMMENT: line over 90 characters
#1539: FILE: examples/vhost_xen/xenstore_parse.c:296:
+ * This function maps grant node of vring or mbuf pool to a continuous virtual address space,
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#1921: FILE: lib/librte_timer/rte_timer.c:186:
+ * mark it atomically as being configured */
total: 0 errors, 6 warnings, 1873 lines checked
parent reply other threads:[~2017-06-07 5:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170607050506.31012-1-jerin.jacob@caviumnetworks.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=20170607050656.39DD82BB8@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jerin.jacob@caviumnetworks.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).