automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-test-report] |WARNING| pw34197 [PATCH v5 3/4] ethdev: reorder inline functions
Date: Mon, 22 Jan 2018 00:36:51 +0100 (CET)	[thread overview]
Message-ID: <20180121233651.212491B16D@dpdk.org> (raw)
In-Reply-To: <20180121233533.95629-3-ferruh.yigit@intel.com>

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

_coding style issues_


WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1075: FILE: lib/librte_ether/rte_ethdev.h:2644:
+ /**
+ * Query Redirection Table(RETA) of Receive Side Scaling of Ethernet device.

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1097: FILE: lib/librte_ether/rte_ethdev.h:2664:
+ /**
+ * Updates unicast hash table for receiving packet with the given destination

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1114: FILE: lib/librte_ether/rte_ethdev.h:2678:
+ *   - (-ENOTSUP) if hardware doesn't support.
+  *  - (-ENODEV) if *port_id* invalid.

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1115: FILE: lib/librte_ether/rte_ethdev.h:2679:
+  *  - (-ENODEV) if *port_id* invalid.
+ *   - (-EIO) if device is removed.

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1122: FILE: lib/librte_ether/rte_ethdev.h:2686:
+ /**
+ * Updates all unicast hash bitmaps for receiving packet with any Unicast

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1141: FILE: lib/librte_ether/rte_ethdev.h:2699:
+ *   - (-ENOTSUP) if hardware doesn't support.
+  *  - (-ENODEV) if *port_id* invalid.

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1142: FILE: lib/librte_ether/rte_ethdev.h:2700:
+  *  - (-ENODEV) if *port_id* invalid.
+ *   - (-EIO) if device is removed.

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1325: FILE: lib/librte_ether/rte_ethdev.h:2769:
+ /**
+ * Configuration of Receive Side Scaling hash computation of Ethernet device.

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1356: FILE: lib/librte_ether/rte_ethdev.h:2786:
+ /**
+ * Retrieve current configuration of Receive Side Scaling hash computation

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1384: FILE: lib/librte_ether/rte_ethdev.h:2804:
+ /**
+ * Add UDP tunneling port for a specific type of tunnel.

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#1419: FILE: lib/librte_ether/rte_ethdev.h:2826:
+ /**
+ * Delete UDP tunneling port a specific type of tunnel.

WARNING:LINE_CONTINUATIONS: Avoid unnecessary line continuations
#2674: FILE: lib/librte_ether/rte_ethdev.h:3596:
+	return (*dev->dev_ops->rx_descriptor_done)( \

total: 0 errors, 12 warnings, 3237 lines checked

           reply	other threads:[~2018-01-21 23:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20180121233533.95629-3-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=20180121233651.212491B16D@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).