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| pw80354 [PATCH v5 2/2] test/crypto: add GMAC SGL tests
Date: Mon, 12 Oct 2020 13:21:38 +0200 (CEST)	[thread overview]
Message-ID: <20201012112138.EEF781D6B7@dpdk.org> (raw)
In-Reply-To: <20201012111913.705225-2-pablo.de.lara.guarch@intel.com>

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

_coding style issues_


WARNING:BLOCK_COMMENT_STYLE: Block comments use * on subsequent lines
#335: FILE: app/test/test_cryptodev_aead_test_vectors.h:2617:
+/* Test vector used to test GMAC SGL with 16 segments
+   plaintext length = ~32KB / segment size = ~2 KB */

WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#335: FILE: app/test/test_cryptodev_aead_test_vectors.h:2617:
+   plaintext length = ~32KB / segment size = ~2 KB */

ERROR:CODE_INDENT: code indent should use tabs where possible
#357: FILE: app/test/test_cryptodev_aead_test_vectors.h:2639:
+                        0xb1, 0xba, 0xe7, 0x28, 0xd3, 0x95, 0x80, 0xd7,$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#357: FILE: app/test/test_cryptodev_aead_test_vectors.h:2639:
+                        0xb1, 0xba, 0xe7, 0x28, 0xd3, 0x95, 0x80, 0xd7,$

ERROR:CODE_INDENT: code indent should use tabs where possible
#358: FILE: app/test/test_cryptodev_aead_test_vectors.h:2640:
+                        0x2e, 0xf5, 0xd0, 0x20, 0x80, 0x95, 0x16, 0x97$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#358: FILE: app/test/test_cryptodev_aead_test_vectors.h:2640:
+                        0x2e, 0xf5, 0xd0, 0x20, 0x80, 0x95, 0x16, 0x97$

total: 2 errors, 4 warnings, 270 lines checked

           reply	other threads:[~2020-10-12 11:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20201012111913.705225-2-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=20201012112138.EEF781D6B7@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).