From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-test-report] |WARNING| pw18436 [PATCH v3] ethdev: cleanup device ops struct whitespace
Date: Thu, 22 Dec 2016 14:10:21 +0100 (CET) [thread overview]
Message-ID: <20161222131021.9F98310D69@dpdk.org> (raw)
In-Reply-To: <20161222131013.28516-1-ferruh.yigit@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/18436
_coding style issues_
WARNING:LONG_LINE_COMMENT: line over 90 characters
#252: FILE: lib/librte_ether/rte_ethdev.h:1465:
+ vlan_pvid_set_t vlan_pvid_set; /**< Set port based TX VLAN insertion. */
WARNING:LONG_LINE_COMMENT: line over 90 characters
#262: FILE: lib/librte_ether/rte_ethdev.h:1475:
+ eth_rx_enable_intr_t rx_queue_intr_enable; /**< Enable Rx queue interrupt. */
WARNING:LONG_LINE_COMMENT: line over 90 characters
#263: FILE: lib/librte_ether/rte_ethdev.h:1476:
+ eth_rx_disable_intr_t rx_queue_intr_disable; /**< Disable Rx queue interrupt. */
WARNING:LONG_LINE_COMMENT: line over 90 characters
#304: FILE: lib/librte_ether/rte_ethdev.h:1485:
+ priority_flow_ctrl_set_t priority_flow_ctrl_set; /**< Setup priority flow control. */
WARNING:LONG_LINE_COMMENT: line over 90 characters
#307: FILE: lib/librte_ether/rte_ethdev.h:1488:
+ eth_uc_all_hash_table_set_t uc_all_hash_table_set; /**< Set Unicast hash bitmap. */
WARNING:LONG_LINE_COMMENT: line over 90 characters
#328: FILE: lib/librte_ether/rte_ethdev.h:1509:
+ rss_hash_conf_get_t rss_hash_conf_get; /** Get current RSS hash configuration. */
total: 0 errors, 6 warnings, 205 lines checked
parent reply other threads:[~2016-12-22 13:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20161222131013.28516-1-ferruh.yigit@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=20161222131021.9F98310D69@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ferruh.yigit@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).