automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: julien_dpdk@jaube.fr
Subject: |WARNING| pw126960 [PATCH] app/test-pmd : Add 2.5Gbps and 5Gbps support to test-pmd
Date: Thu, 18 May 2023 01:17:29 +0200 (CEST)	[thread overview]
Message-ID: <20230517231729.BB9A2120927@dpdk.org> (raw)
In-Reply-To: <20230517231614.69440-1-julien_dpdk@jaube.fr>

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

_coding style issues_


ERROR:CODE_INDENT: code indent should use tabs where possible
#83: FILE: app/test-pmd/cmdline.c:1348:
+                        *speed = RTE_ETH_LINK_SPEED_2_5G;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#83: FILE: app/test-pmd/cmdline.c:1348:
+                        *speed = RTE_ETH_LINK_SPEED_2_5G;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#84: FILE: app/test-pmd/cmdline.c:1349:
+                } else if (!strcmp(speedstr, "5000")) {$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#84: FILE: app/test-pmd/cmdline.c:1349:
+                } else if (!strcmp(speedstr, "5000")) {$

ERROR:CODE_INDENT: code indent should use tabs where possible
#85: FILE: app/test-pmd/cmdline.c:1350:
+                        *speed = RTE_ETH_LINK_SPEED_5G;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#85: FILE: app/test-pmd/cmdline.c:1350:
+                        *speed = RTE_ETH_LINK_SPEED_5G;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#86: FILE: app/test-pmd/cmdline.c:1351:
+                } else if (!strcmp(speedstr, "10000")) {$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#86: FILE: app/test-pmd/cmdline.c:1351:
+                } else if (!strcmp(speedstr, "10000")) {$

ERROR:CODE_INDENT: code indent should use tabs where possible
#134: FILE: app/test-pmd/parameters.c:553:
+        case 2500:$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#134: FILE: app/test-pmd/parameters.c:553:
+        case 2500:$

ERROR:CODE_INDENT: code indent should use tabs where possible
#135: FILE: app/test-pmd/parameters.c:554:
+                speed |= RTE_ETH_LINK_SPEED_2_5G;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#135: FILE: app/test-pmd/parameters.c:554:
+                speed |= RTE_ETH_LINK_SPEED_2_5G;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#136: FILE: app/test-pmd/parameters.c:555:
+                break;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#136: FILE: app/test-pmd/parameters.c:555:
+                break;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#137: FILE: app/test-pmd/parameters.c:556:
+        case 5000:$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#137: FILE: app/test-pmd/parameters.c:556:
+        case 5000:$

ERROR:CODE_INDENT: code indent should use tabs where possible
#138: FILE: app/test-pmd/parameters.c:557:
+                speed |= RTE_ETH_LINK_SPEED_5G;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#138: FILE: app/test-pmd/parameters.c:557:
+                speed |= RTE_ETH_LINK_SPEED_5G;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#139: FILE: app/test-pmd/parameters.c:558:
+                break;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#139: FILE: app/test-pmd/parameters.c:558:
+                break;$

total: 10 errors, 10 warnings, 80 lines checked

       reply	other threads:[~2023-05-17 23:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230517231614.69440-1-julien_dpdk@jaube.fr>
2023-05-17 23:17 ` checkpatch [this message]
2023-05-17 23:17 ` |SUCCESS| " qemudev
2023-05-17 23:21 ` qemudev
2023-05-18  0:20 ` 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=20230517231729.BB9A2120927@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=julien_dpdk@jaube.fr \
    --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).