automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Dekel Peled <dekelp@mellanox.com>
Subject: [dpdk-test-report] |WARNING| pw75149 [RFC v2] ethdev: add extensions attributes to IPv6 item
Date: Mon,  3 Aug 2020 19:05:03 +0200 (CEST)	[thread overview]
Message-ID: <20200803170503.9C2C72E8F@dpdk.org> (raw)
In-Reply-To: <33de39c7ef627b87f5e0bb34f364a92fffc39fc5.1596470130.git.dekelp@mellanox.com>

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

_coding style issues_


ERROR:CODE_INDENT: code indent should use tabs where possible
#104: FILE: lib/librte_ethdev/rte_flow.h:804:
+        uint64_t rout_ext_exist:1;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#104: FILE: lib/librte_ethdev/rte_flow.h:804:
+        uint64_t rout_ext_exist:1;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#105: FILE: lib/librte_ethdev/rte_flow.h:805:
+        /**< Routing extension header exists. */$

ERROR:CODE_INDENT: code indent should use tabs where possible
#106: FILE: lib/librte_ethdev/rte_flow.h:806:
+        uint64_t frag_ext_exist:1;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#106: FILE: lib/librte_ethdev/rte_flow.h:806:
+        uint64_t frag_ext_exist:1;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#107: FILE: lib/librte_ethdev/rte_flow.h:807:
+        /**< Fragment extension header exists. */$

ERROR:CODE_INDENT: code indent should use tabs where possible
#108: FILE: lib/librte_ethdev/rte_flow.h:808:
+        uint64_t auth_ext_exist:1;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#108: FILE: lib/librte_ethdev/rte_flow.h:808:
+        uint64_t auth_ext_exist:1;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#109: FILE: lib/librte_ethdev/rte_flow.h:809:
+        /**< Authentication extension header exists. */$

ERROR:CODE_INDENT: code indent should use tabs where possible
#110: FILE: lib/librte_ethdev/rte_flow.h:810:
+        uint64_t esp_ext_exist:1;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#110: FILE: lib/librte_ethdev/rte_flow.h:810:
+        uint64_t esp_ext_exist:1;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#111: FILE: lib/librte_ethdev/rte_flow.h:811:
+        /**< Encapsulation Security Payload extension header exists. */$

ERROR:CODE_INDENT: code indent should use tabs where possible
#112: FILE: lib/librte_ethdev/rte_flow.h:812:
+        uint64_t dest_ext_exist:1;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#112: FILE: lib/librte_ethdev/rte_flow.h:812:
+        uint64_t dest_ext_exist:1;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#113: FILE: lib/librte_ethdev/rte_flow.h:813:
+        /**< Destination Options extension header exists. */$

ERROR:CODE_INDENT: code indent should use tabs where possible
#114: FILE: lib/librte_ethdev/rte_flow.h:814:
+        uint64_t mobil_ext_exist:1;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#114: FILE: lib/librte_ethdev/rte_flow.h:814:
+        uint64_t mobil_ext_exist:1;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#115: FILE: lib/librte_ethdev/rte_flow.h:815:
+        /**< Mobility extension header exists. */$

ERROR:CODE_INDENT: code indent should use tabs where possible
#116: FILE: lib/librte_ethdev/rte_flow.h:816:
+        uint64_t hip_ext_exist:1;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#116: FILE: lib/librte_ethdev/rte_flow.h:816:
+        uint64_t hip_ext_exist:1;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#117: FILE: lib/librte_ethdev/rte_flow.h:817:
+        /**< Host Identity Protocol extension header exists. */$

ERROR:CODE_INDENT: code indent should use tabs where possible
#118: FILE: lib/librte_ethdev/rte_flow.h:818:
+        uint64_t shim6_ext_exist:1;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#118: FILE: lib/librte_ethdev/rte_flow.h:818:
+        uint64_t shim6_ext_exist:1;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#119: FILE: lib/librte_ethdev/rte_flow.h:819:
+        /**< Shim6 Protocol extension header exists. */$

ERROR:CODE_INDENT: code indent should use tabs where possible
#120: FILE: lib/librte_ethdev/rte_flow.h:820:
+        uint64_t reserved:55;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#120: FILE: lib/librte_ethdev/rte_flow.h:820:
+        uint64_t reserved:55;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#121: FILE: lib/librte_ethdev/rte_flow.h:821:
+        /**< Reserved for future extension headers, must be zero. */$

total: 18 errors, 9 warnings, 33 lines checked

           reply	other threads:[~2020-08-03 17:05 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <33de39c7ef627b87f5e0bb34f364a92fffc39fc5.1596470130.git.dekelp@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=20200803170503.9C2C72E8F@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=dekelp@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).