From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Fan Zhang <roy.fan.zhang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw60636 [PATCH v2 03/10] app/test: add security cpu crypto autotest
Date: Mon, 7 Oct 2019 18:30:35 +0200 (CEST) [thread overview]
Message-ID: <20191007163035.84E941D149@dpdk.org> (raw)
In-Reply-To: <20191007162850.60552-4-roy.fan.zhang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/60636
_coding style issues_
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#550: FILE: app/test/test_security_cpu_crypto.c:494:
+#define all_gcm_unit_test_cases(type) \
+ TEST_EXPAND(gcm_test_case_1, type) \
+ TEST_EXPAND(gcm_test_case_2, type) \
+ TEST_EXPAND(gcm_test_case_3, type) \
+ TEST_EXPAND(gcm_test_case_4, type) \
+ TEST_EXPAND(gcm_test_case_5, type) \
+ TEST_EXPAND(gcm_test_case_6, type) \
+ TEST_EXPAND(gcm_test_case_7, type) \
+ TEST_EXPAND(gcm_test_case_8, type) \
+ TEST_EXPAND(gcm_test_case_192_1, type) \
+ TEST_EXPAND(gcm_test_case_192_2, type) \
+ TEST_EXPAND(gcm_test_case_192_3, type) \
+ TEST_EXPAND(gcm_test_case_192_4, type) \
+ TEST_EXPAND(gcm_test_case_192_5, type) \
+ TEST_EXPAND(gcm_test_case_192_6, type) \
+ TEST_EXPAND(gcm_test_case_192_7, type) \
+ TEST_EXPAND(gcm_test_case_256_1, type) \
+ TEST_EXPAND(gcm_test_case_256_2, type) \
+ TEST_EXPAND(gcm_test_case_256_3, type) \
+ TEST_EXPAND(gcm_test_case_256_4, type) \
+ TEST_EXPAND(gcm_test_case_256_5, type) \
+ TEST_EXPAND(gcm_test_case_256_6, type) \
+ TEST_EXPAND(gcm_test_case_256_7, type)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#596: FILE: app/test/test_security_cpu_crypto.c:540:
+#define TEST_EXPAND(t, o) \
+ TEST_CASE_ST(ut_setup, ut_teardown, \
+ cpu_crypto_aead_enc_test_##t##_##o), \
+ TEST_CASE_ST(ut_setup, ut_teardown, \
+ cpu_crypto_aead_dec_test_##t##_##o), \
+
total: 2 errors, 0 warnings, 578 lines checked
parent reply other threads:[~2019-10-07 16:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20191007162850.60552-4-roy.fan.zhang@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=20191007163035.84E941D149@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=roy.fan.zhang@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).