automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gregory Etelson <getelson@nvidia.com>
Subject: |WARNING| pw127112 [PATCH v4] ethdev: add indirect list flow action
Date: Fri, 19 May 2023 14:01:15 +0200 (CEST)	[thread overview]
Message-ID: <20230519120115.5D93F120927@dpdk.org> (raw)
In-Reply-To: <20230519115947.331304-1-getelson@nvidia.com>

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

_coding style issues_


ERROR:CODE_INDENT: code indent should use tabs where possible
#387: FILE: app/test-pmd/cmdline_flow.c:6826:
+^I^I^I^I           rte_flow_action_indirect_list)),$

ERROR:CODE_INDENT: code indent should use tabs where possible
#442: FILE: app/test-pmd/cmdline_flow.c:7273:
+        case INDIRECT_ACTION_FLOW_CONF:$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#442: FILE: app/test-pmd/cmdline_flow.c:7273:
+        case INDIRECT_ACTION_FLOW_CONF:$

ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#479: FILE: app/test-pmd/cmdline_flow.c:10515:
+		    void __rte_unused *buf, unsigned int __rte_unused size)
 		                      ^

ERROR:CODE_INDENT: code indent should use tabs where possible
#500: FILE: app/test-pmd/cmdline_flow.c:10536:
+        action_conf->handle = (typeof(action_conf->handle))$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#500: FILE: app/test-pmd/cmdline_flow.c:10536:
+        action_conf->handle = (typeof(action_conf->handle))$

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 8)
#564: FILE: app/test-pmd/cmdline_flow.c:11634:
+	if (indlst_conf)
+        printf("created indirect action list configuration %u
",

ERROR:CODE_INDENT: code indent should use tabs where possible
#565: FILE: app/test-pmd/cmdline_flow.c:11635:
+        printf("created indirect action list configuration %u
",$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#565: FILE: app/test-pmd/cmdline_flow.c:11635:
+        printf("created indirect action list configuration %u
",$

ERROR:CODE_INDENT: code indent should use tabs where possible
#566: FILE: app/test-pmd/cmdline_flow.c:11636:
+               in->args.vc.attr.group);$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#566: FILE: app/test-pmd/cmdline_flow.c:11636:
+               in->args.vc.attr.group);$

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 8)
#567: FILE: app/test-pmd/cmdline_flow.c:11637:
+	else
+        printf("cannot create indirect action list configuration %u
",

ERROR:CODE_INDENT: code indent should use tabs where possible
#568: FILE: app/test-pmd/cmdline_flow.c:11638:
+        printf("cannot create indirect action list configuration %u
",$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#568: FILE: app/test-pmd/cmdline_flow.c:11638:
+        printf("cannot create indirect action list configuration %u
",$

ERROR:CODE_INDENT: code indent should use tabs where possible
#569: FILE: app/test-pmd/cmdline_flow.c:11639:
+               in->args.vc.attr.group);$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#569: FILE: app/test-pmd/cmdline_flow.c:11639:
+               in->args.vc.attr.group);$

ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#1244: FILE: lib/ethdev/rte_flow.c:2230:
+					      rte_flow_indir_action_conf *conf,
 					                                 ^

WARNING:FUNCTION_ARGUMENTS: arguments for function declarations should follow identifier
#1273: FILE: lib/ethdev/rte_flow.c:2259:
+int

WARNING:FUNCTION_ARGUMENTS: arguments for function declarations should follow identifier
#1300: FILE: lib/ethdev/rte_flow.c:2286:
+int

WARNING:FUNCTION_ARGUMENTS: arguments for function declarations should follow identifier
#1327: FILE: lib/ethdev/rte_flow.c:2313:
+int

ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#1480: FILE: lib/ethdev/rte_flow.h:6227:
+					 rte_flow_indir_action_conf *conf,
 					                            ^

ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#1589: FILE: lib/ethdev/rte_flow.h:6336:
+					 rte_flow_action_list_handle *handle,
 					                             ^

ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#1636: FILE: lib/ethdev/rte_flow.h:6383:
+					  rte_flow_action_list_handle *handle,
 					                              ^

total: 12 errors, 11 warnings, 1389 lines checked

  parent reply	other threads:[~2023-05-19 12:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230519115947.331304-1-getelson@nvidia.com>
2023-05-19 11:50 ` |SUCCESS| " qemudev
2023-05-19 11:54 ` qemudev
2023-05-19 12:01 ` checkpatch [this message]
2023-05-19 12:59 ` 0-day Robot

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=20230519120115.5D93F120927@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=getelson@nvidia.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).