automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Yogesh Jangra <yogesh.jangra@intel.com>
Subject: [dpdk-test-report] |WARNING| pw81784 [PATCH] examples/pipeline: fix help command
Date: Thu, 22 Oct 2020 12:41:07 +0200 (CEST)	[thread overview]
Message-ID: <20201022104107.136A6A9BA@dpdk.org> (raw)
In-Reply-To: <1603363174-22370-1-git-send-email-yogesh.jangra@intel.com>

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

_coding style issues_


ERROR:CODE_INDENT: code indent should use tabs where possible
#89: FILE: examples/pipeline/cli.c:1168:
+                        "	mempool
"$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#89: FILE: examples/pipeline/cli.c:1168:
+                        "	mempool
"$

ERROR:CODE_INDENT: code indent should use tabs where possible
#90: FILE: examples/pipeline/cli.c:1169:
+                        "	link
"$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#90: FILE: examples/pipeline/cli.c:1169:
+                        "	link
"$

ERROR:CODE_INDENT: code indent should use tabs where possible
#92: FILE: examples/pipeline/cli.c:1171:
+                        "	pipeline port in
"$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#92: FILE: examples/pipeline/cli.c:1171:
+                        "	pipeline port in
"$

ERROR:CODE_INDENT: code indent should use tabs where possible
#93: FILE: examples/pipeline/cli.c:1172:
+                        "	pipeline port out
"$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#93: FILE: examples/pipeline/cli.c:1172:
+                        "	pipeline port out
"$

ERROR:CODE_INDENT: code indent should use tabs where possible
#95: FILE: examples/pipeline/cli.c:1174:
+                        "	pipeline table update
"$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#95: FILE: examples/pipeline/cli.c:1174:
+                        "	pipeline table update
"$

ERROR:CODE_INDENT: code indent should use tabs where possible
#97: FILE: examples/pipeline/cli.c:1176:
+                        "	thread pipeline enable
"$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#97: FILE: examples/pipeline/cli.c:1176:
+                        "	thread pipeline enable
"$

ERROR:CODE_INDENT: code indent should use tabs where possible
#98: FILE: examples/pipeline/cli.c:1177:
+                        "	thread pipeline disable

");$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#98: FILE: examples/pipeline/cli.c:1177:
+                        "	thread pipeline disable

");$

total: 7 errors, 7 warnings, 76 lines checked

       reply	other threads:[~2020-10-22 10:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1603363174-22370-1-git-send-email-yogesh.jangra@intel.com>
2020-10-22 10:41 ` checkpatch [this message]
2020-10-22 21:28 ` [dpdk-test-report] |SUCCESS| pw81784 " 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=20201022104107.136A6A9BA@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=yogesh.jangra@intel.com \
    /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).