From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Mairtin o Loingsigh <mairtin.oloingsigh@intel.com>
Subject: [dpdk-test-report] |WARNING| pw67868 [PATCH v2 2/2] test/crypto: Add AES-256 DOCSIS test vectors
Date: Mon, 6 Apr 2020 17:37:00 +0200 (CEST) [thread overview]
Message-ID: <20200406153700.ECE401BF59@dpdk.org> (raw)
In-Reply-To: <1586187346-19020-2-git-send-email-mairtin.oloingsigh@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/67868
_coding style issues_
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#100: FILE: app/test/test_cryptodev_aes_test_vectors.h:2751:
+#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#112: FILE: app/test/test_cryptodev_aes_test_vectors.h:2763:
+#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#124: FILE: app/test/test_cryptodev_aes_test_vectors.h:2775:
+#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#136: FILE: app/test/test_cryptodev_aes_test_vectors.h:2787:
+#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#148: FILE: app/test/test_cryptodev_aes_test_vectors.h:2799:
+#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#160: FILE: app/test/test_cryptodev_aes_test_vectors.h:2811:
+#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#173: FILE: app/test/test_cryptodev_aes_test_vectors.h:2824:
+#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#186: FILE: app/test/test_cryptodev_aes_test_vectors.h:2837:
+#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#199: FILE: app/test/test_cryptodev_aes_test_vectors.h:2850:
+#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#212: FILE: app/test/test_cryptodev_aes_test_vectors.h:2863:
+#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#225: FILE: app/test/test_cryptodev_aes_test_vectors.h:2876:
+#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
WARNING:CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test
#238: FILE: app/test/test_cryptodev_aes_test_vectors.h:2889:
+#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
total: 0 errors, 12 warnings, 166 lines checked
next parent reply other threads:[~2020-04-06 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1586187346-19020-2-git-send-email-mairtin.oloingsigh@intel.com>
2020-04-06 15:37 ` checkpatch [this message]
2020-04-06 17:10 ` [dpdk-test-report] |SUCCESS| pw67868 crypto/aesni_mb: support DOCSIS AES-256 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=20200406153700.ECE401BF59@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=mairtin.oloingsigh@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).