[dpdk-test-report] |WARNING| pw40660 [PATCH RFC] ethdev: support tunnel encapsulation action

automatic DPDK test reports
 help / color / mirror / Atom feed

From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ori Kam <orika@mellanox.com>
Subject: [dpdk-test-report] |WARNING| pw40660 [PATCH RFC] ethdev: support tunnel encapsulation action
Date: Tue,  5 Jun 2018 17:50:13 +0200 (CEST)	[thread overview]
Message-ID: <20180605155013.0B9071BAAC@dpdk.org> (raw)
In-Reply-To: <1528213708-5247-1-git-send-email-orika@mellanox.com>

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

_coding style issues_


ERROR:TRAILING_WHITESPACE: trailing whitespace
#93: FILE: doc/guides/prog_guide/rte_flow.rst:1984:
+    $

ERROR:TRAILING_WHITESPACE: trailing whitespace
#145: FILE: doc/guides/prog_guide/rte_flow.rst:2006:
+    $

ERROR:TRAILING_WHITESPACE: trailing whitespace
#176: FILE: doc/guides/prog_guide/rte_flow.rst:2027:
+    $

WARNING:TYPO_SPELLING: 'suplied' may be misspelled - perhaps 'supplied'?
#209: FILE: doc/guides/prog_guide/rte_flow.rst:2042:
+and adding the L2 header which is suplied in the buf parameter.

ERROR:TRAILING_WHITESPACE: trailing whitespace
#225: FILE: doc/guides/prog_guide/rte_flow.rst:2051:
+    $

ERROR:CODE_INDENT: code indent should use tabs where possible
#248: FILE: lib/librte_ethdev/rte_flow.h:1476:
+ ^I * Encapsulte a packet with tunnel header.$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#248: FILE: lib/librte_ethdev/rte_flow.h:1476:
+ ^I * Encapsulte a packet with tunnel header.$

ERROR:CODE_INDENT: code indent should use tabs where possible
#249: FILE: lib/librte_ethdev/rte_flow.h:1477:
+ ^I *$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#249: FILE: lib/librte_ethdev/rte_flow.h:1477:
+ ^I *$

ERROR:CODE_INDENT: code indent should use tabs where possible
#250: FILE: lib/librte_ethdev/rte_flow.h:1478:
+ ^I * See struct rte_flow_action_tunnel_encap.$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#250: FILE: lib/librte_ethdev/rte_flow.h:1478:
+ ^I * See struct rte_flow_action_tunnel_encap.$

ERROR:CODE_INDENT: code indent should use tabs where possible
#251: FILE: lib/librte_ethdev/rte_flow.h:1479:
+ ^I */$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#251: FILE: lib/librte_ethdev/rte_flow.h:1479:
+ ^I */$

ERROR:CODE_INDENT: code indent should use tabs where possible
#255: FILE: lib/librte_ethdev/rte_flow.h:1483:
+ ^I * Encapsulte a packet with tunnel header replacing$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#255: FILE: lib/librte_ethdev/rte_flow.h:1483:
+ ^I * Encapsulte a packet with tunnel header replacing$

ERROR:CODE_INDENT: code indent should use tabs where possible
#256: FILE: lib/librte_ethdev/rte_flow.h:1484:
+ ^I * the inner L2 data.$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#256: FILE: lib/librte_ethdev/rte_flow.h:1484:
+ ^I * the inner L2 data.$

ERROR:CODE_INDENT: code indent should use tabs where possible
#257: FILE: lib/librte_ethdev/rte_flow.h:1485:
+ ^I *$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#257: FILE: lib/librte_ethdev/rte_flow.h:1485:
+ ^I *$

ERROR:CODE_INDENT: code indent should use tabs where possible
#258: FILE: lib/librte_ethdev/rte_flow.h:1486:
+ ^I * See struct rte_flow_action_tunnel_encap_l3.$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#258: FILE: lib/librte_ethdev/rte_flow.h:1486:
+ ^I * See struct rte_flow_action_tunnel_encap_l3.$

ERROR:CODE_INDENT: code indent should use tabs where possible
#259: FILE: lib/librte_ethdev/rte_flow.h:1487:
+ ^I */$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#259: FILE: lib/librte_ethdev/rte_flow.h:1487:
+ ^I */$

total: 13 errors, 10 warnings, 389 lines checked

          parent reply	other threads:[~2018-06-05 15:50 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1528213708-5247-1-git-send-email-orika@mellanox.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=20180605155013.0B9071BAAC@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=orika@mellanox.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).