From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gaetan Rivet <gaetan.rivet@6wind.com>
Subject: [dpdk-test-report] |WARNING| pw36400 [PATCH v2 09/18] eal/dev: implement device iteration
Date: Wed, 21 Mar 2018 18:17:49 +0100 (CET) [thread overview]
Message-ID: <20180321171749.61BC5728A@dpdk.org> (raw)
In-Reply-To: <390e98e1afddd5c80ba243efc44b8a047ea68710.1521652453.git.gaetan.rivet@6wind.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/36400
_coding style issues_
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#45: FILE: lib/librte_eal/common/eal_common_dev.c:35:
+#define ITCTX(ptr) \
+ ((struct dev_next_ctx *)(intptr_t)ptr)->it
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#48: FILE: lib/librte_eal/common/eal_common_dev.c:38:
+#define BUSCTX(ptr) \
+ ((struct dev_next_ctx *)(intptr_t)ptr)->busstr
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#51: FILE: lib/librte_eal/common/eal_common_dev.c:41:
+#define CLSCTX(ptr) \
+ ((struct dev_next_ctx *)(intptr_t)ptr)->clsstr
total: 3 errors, 0 warnings, 206 lines checked
parent reply other threads:[~2018-03-21 17:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <390e98e1afddd5c80ba243efc44b8a047ea68710.1521652453.git.gaetan.rivet@6wind.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=20180321171749.61BC5728A@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=gaetan.rivet@6wind.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).