automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-test-report] |WARNING| pw68426 [PATCH 1/2] test/crypto: add capability check
Date: Tue, 14 Apr 2020 12:24:27 +0200 (CEST)	[thread overview]
Message-ID: <20200414102427.D930B1C1FE@dpdk.org> (raw)
In-Reply-To: <1586859760-207446-1-git-send-email-pablo.de.lara.guarch@intel.com>

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

_coding style issues_


ERROR:CODE_INDENT: code indent should use tabs where possible
#114: FILE: app/test/test_cryptodev_blockcipher.c:61:
+        return 0;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#114: FILE: app/test/test_cryptodev_blockcipher.c:61:
+        return 0;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#125: FILE: app/test/test_cryptodev_blockcipher.c:156:
+        /* Check if PMD is capable of performing that test */$

ERROR:CODE_INDENT: code indent should use tabs where possible
#126: FILE: app/test/test_cryptodev_blockcipher.c:157:
+        if (verify_algo_support(t, dev_id, digest_len) < 0) {$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#126: FILE: app/test/test_cryptodev_blockcipher.c:157:
+        if (verify_algo_support(t, dev_id, digest_len) < 0) {$

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 17)
#126: FILE: app/test/test_cryptodev_blockcipher.c:157:
+        if (verify_algo_support(t, dev_id, digest_len) < 0) {
+		 RTE_LOG(DEBUG, USER1,

total: 3 errors, 3 warnings, 61 lines checked

           reply	other threads:[~2020-04-14 10:24 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1586859760-207446-1-git-send-email-pablo.de.lara.guarch@intel.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=20200414102427.D930B1C1FE@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.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).