From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Subject: [dpdk-test-report] |WARNING| pw59138 [PATCH v5 12/12] test/fib: add FIB library ipv6 performance autotests
Date: Wed, 11 Sep 2019 19:12:04 +0200 (CEST) [thread overview]
Message-ID: <20190911171204.ED2001E888@dpdk.org> (raw)
In-Reply-To: <de543f02c7c80be474178672cecf414a224eb1cd.1568221365.git.vladimir.medvedkin@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/59138
_coding style issues_
WARNING:MACRO_WITH_FLOW_CONTROL: Macros with flow control statements should be avoided
#100: FILE: app/test/test_fib6_perf.c:18:
+#define TEST_FIB_ASSERT(cond) do { \
+ if (!(cond)) { \
+ printf("Error at line %d:
", __LINE__); \
+ return -1; \
+ } \
+} while (0)
total: 0 errors, 1 warnings, 190 lines checked
parent reply other threads:[~2019-09-11 17:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <de543f02c7c80be474178672cecf414a224eb1cd.1568221365.git.vladimir.medvedkin@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=20190911171204.ED2001E888@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=vladimir.medvedkin@intel.com \
/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).