automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Akhil Goyal <gakhil@marvell.com>
Subject: |WARNING| pw140270 [PATCH] test/crypto: fix enqueue dequeue callback case
Date: Wed, 22 May 2024 15:49:15 +0200 (CEST)	[thread overview]
Message-ID: <20240522134915.CB5FB12367B@dpdk.org> (raw)
In-Reply-To: <20240522134835.3453044-1-gakhil@marvell.com>

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

_coding style issues_


WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#202: FILE: app/test/test_cryptodev.c:14844:
+	 * hence the PMD should support these algos. */

ERROR:CODE_INDENT: code indent should use tabs where possible
#212: FILE: app/test/test_cryptodev.c:14854:
+ ^I^Ireturn TEST_SKIPPED;$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#212: FILE: app/test/test_cryptodev.c:14854:
+ ^I^Ireturn TEST_SKIPPED;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#212: FILE: app/test/test_cryptodev.c:14854:
+ ^I^Ireturn TEST_SKIPPED;$

ERROR:TRAILING_WHITESPACE: trailing whitespace
#213: FILE: app/test/test_cryptodev.c:14855:
+ $

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#213: FILE: app/test/test_cryptodev.c:14855:
+ $

total: 2 errors, 4 warnings, 134 lines checked

  parent reply	other threads:[~2024-05-22 13:49 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240522134835.3453044-1-gakhil@marvell.com>
2024-05-22 13:21 ` |SUCCESS| " qemudev
2024-05-22 13:26 ` qemudev
2024-05-22 13:49 ` checkpatch [this message]
2024-05-22 14:33 ` |SUCCESS| pw140270 [PATCH] test/crypto: fix enqueue dequeue callback dpdklab
2024-05-22 14:34 ` dpdklab
2024-05-22 14:35 ` dpdklab
2024-05-22 14:36 ` dpdklab
2024-05-22 14:37 ` dpdklab
2024-05-22 14:37 ` dpdklab
2024-05-22 14:37 ` dpdklab
2024-05-22 14:38 ` dpdklab
2024-05-22 14:38 ` dpdklab
2024-05-22 14:39 ` dpdklab
2024-05-22 14:40 ` dpdklab
2024-05-22 14:40 ` dpdklab
2024-05-22 14:41 ` dpdklab
2024-05-22 14:42 ` dpdklab
2024-05-22 14:43 ` dpdklab
2024-05-22 14:44 ` |FAILURE| " dpdklab
2024-05-22 14:44 ` |SUCCESS| pw140270 [PATCH] test/crypto: fix enqueue dequeue callback case 0-day Robot
2024-05-22 14:44 ` |SUCCESS| pw140270 [PATCH] test/crypto: fix enqueue dequeue callback dpdklab
2024-05-22 14:44 ` dpdklab
2024-05-22 14:45 ` dpdklab
2024-05-22 14:45 ` dpdklab
2024-05-22 14:45 ` dpdklab
2024-05-22 14:45 ` |FAILURE| " dpdklab
2024-05-22 14:46 ` dpdklab
2024-05-22 14:46 ` |SUCCESS| " dpdklab
2024-05-22 14:46 ` dpdklab
2024-05-22 14:46 ` |FAILURE| " dpdklab
2024-05-22 14:47 ` |SUCCESS| " dpdklab
2024-05-22 14:47 ` dpdklab
2024-05-22 14:48 ` dpdklab
2024-05-22 14:48 ` dpdklab
2024-05-22 14:48 ` dpdklab
2024-05-22 14:48 ` |FAILURE| " dpdklab
2024-05-22 14:49 ` |SUCCESS| " dpdklab
2024-05-22 14:49 ` dpdklab
2024-05-22 14:49 ` dpdklab
2024-05-22 14:49 ` dpdklab
2024-05-22 14:49 ` |FAILURE| " dpdklab
2024-05-22 14:50 ` dpdklab
2024-05-22 14:50 ` |SUCCESS| " dpdklab
2024-05-22 14:50 ` dpdklab
2024-05-22 14:50 ` dpdklab
2024-05-22 14:51 ` dpdklab
2024-05-22 14:51 ` |FAILURE| " dpdklab
2024-05-22 14:51 ` |SUCCESS| " dpdklab
2024-05-22 14:51 ` dpdklab
2024-05-22 14:51 ` dpdklab
2024-05-22 14:52 ` dpdklab
2024-05-22 14:52 ` dpdklab
2024-05-22 14:52 ` dpdklab
2024-05-22 14:52 ` |FAILURE| " dpdklab
2024-05-22 14:52 ` |SUCCESS| " dpdklab
2024-05-22 14:52 ` |FAILURE| " dpdklab
2024-05-22 14:53 ` |SUCCESS| " dpdklab
2024-05-22 14:53 ` |FAILURE| " dpdklab
2024-05-22 14:53 ` |SUCCESS| " dpdklab
2024-05-22 14:53 ` |FAILURE| " dpdklab
2024-05-22 14:53 ` |SUCCESS| " dpdklab
2024-05-22 14:53 ` dpdklab
2024-05-22 14:54 ` dpdklab
2024-05-22 14:54 ` dpdklab
2024-05-22 14:54 ` |FAILURE| " dpdklab
2024-05-22 14:54 ` dpdklab
2024-05-22 14:54 ` dpdklab
2024-05-22 14:54 ` |SUCCESS| " dpdklab
2024-05-22 14:54 ` dpdklab
2024-05-22 14:55 ` |FAILURE| " dpdklab
2024-05-22 14:56 ` dpdklab
2024-05-22 14:57 ` dpdklab
2024-05-22 15:00 ` dpdklab
2024-05-22 15:00 ` dpdklab
2024-05-22 15:03 ` dpdklab
2024-05-22 15:03 ` dpdklab
2024-05-22 15:06 ` dpdklab
2024-05-22 15:06 ` |SUCCESS| " dpdklab
2024-05-22 15:08 ` |FAILURE| " dpdklab
2024-05-22 15:10 ` |SUCCESS| " dpdklab
2024-05-22 15:11 ` |FAILURE| " dpdklab
2024-05-22 15:12 ` |SUCCESS| " dpdklab
2024-05-22 15:22 ` |FAILURE| " dpdklab
2024-05-22 15:25 ` |SUCCESS| " dpdklab
2024-05-22 15:59 ` dpdklab
2024-05-22 18:04 ` dpdklab
2024-05-23  6:09 ` dpdklab

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=20240522134915.CB5FB12367B@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=gakhil@marvell.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).