From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-test-report] |WARNING| pw33264 [PATCH v2 4/6] ethdev: reorder inline functions
Date: Tue, 9 Jan 2018 17:24:37 +0100 (CET) [thread overview]
Message-ID: <20180109162437.04E671B1E4@dpdk.org> (raw)
In-Reply-To: <20180109162317.18183-4-ferruh.yigit@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/33264
_coding style issues_
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1039: FILE: lib/librte_ether/rte_ethdev.h:2579:
+ /**
+ * Query Redirection Table(RETA) of Receive Side Scaling of Ethernet device.
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1060: FILE: lib/librte_ether/rte_ethdev.h:2598:
+ /**
+ * Updates unicast hash table for receiving packet with the given destination
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1077: FILE: lib/librte_ether/rte_ethdev.h:2612:
+ * - (-ENOTSUP) if hardware doesn't support.
+ * - (-ENODEV) if *port_id* invalid.
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1078: FILE: lib/librte_ether/rte_ethdev.h:2613:
+ * - (-ENODEV) if *port_id* invalid.
+ * - (-EINVAL) if bad parameter.
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1084: FILE: lib/librte_ether/rte_ethdev.h:2619:
+ /**
+ * Updates all unicast hash bitmaps for receiving packet with any Unicast
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1103: FILE: lib/librte_ether/rte_ethdev.h:2632:
+ * - (-ENOTSUP) if hardware doesn't support.
+ * - (-ENODEV) if *port_id* invalid.
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1104: FILE: lib/librte_ether/rte_ethdev.h:2633:
+ * - (-ENODEV) if *port_id* invalid.
+ * - (-EINVAL) if bad parameter.
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1278: FILE: lib/librte_ether/rte_ethdev.h:2698:
+ /**
+ * Configuration of Receive Side Scaling hash computation of Ethernet device.
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1308: FILE: lib/librte_ether/rte_ethdev.h:2714:
+ /**
+ * Retrieve current configuration of Receive Side Scaling hash computation
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1335: FILE: lib/librte_ether/rte_ethdev.h:2731:
+ /**
+ * Add UDP tunneling port for a specific type of tunnel.
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1369: FILE: lib/librte_ether/rte_ethdev.h:2752:
+ /**
+ * Delete UDP tunneling port a specific type of tunnel.
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#2228: FILE: lib/librte_ether/rte_ethdev.h:3276:
+/**
+* Get the device name from port id
WARNING:LINE_CONTINUATIONS: Avoid unnecessary line continuations
#2544: FILE: lib/librte_ether/rte_ethdev.h:3491:
+ return (*dev->dev_ops->rx_descriptor_done)( \
total: 0 errors, 13 warnings, 3127 lines checked
parent reply other threads:[~2018-01-09 16:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180109162317.18183-4-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=20180109162437.04E671B1E4@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).