From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw70930 [PATCH 4/9] eal: replace usage of blacklist/whitelist in enum
Date: Wed, 10 Jun 2020 09:56:26 +0200 (CEST) [thread overview]
Message-ID: <20200610075626.7E9AD2BFA@dpdk.org> (raw)
In-Reply-To: <20200607170127.15694-5-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/70930
_coding style issues_
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#144: FILE: lib/librte_eal/include/rte_bus.h:222:
+#define RTE_BUS_SCAN_WHITELIST \
+ _Pragma("GCC message \"RTE_BUS_SCAN_WHITELIST\" is deprecated\"") \
+ RTE_BUS_SCAN_ALLOWLIST
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#148: FILE: lib/librte_eal/include/rte_bus.h:226:
+#define RTE_BUS_SCAN_BLACKLIST \
+ _Pragma("GCC message \"RTE_BUS_SCAN_BLACKLIST\" is deprecated\"") \
+ RTE_BUS_SCAN_BLOCKLIST
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#169: FILE: lib/librte_eal/include/rte_dev.h:77:
+#define RTE_DEV_WHITELISTED \
+ _Pragma("GCC message \"'RTE_DEV_WHITELISTED' is deprecated\"") \
+ RTE_DEV_ALLOWLIST
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#173: FILE: lib/librte_eal/include/rte_dev.h:81:
+#define RTE_DEV_BLACKLISTED \
+ _Pragma("GCC message \"'RTE_DEV_BLACKLISTED' is deprecated\"") \
+ RTE_DEV_BLOCKLIST
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#195: FILE: lib/librte_eal/include/rte_devargs.h:37:
+#define RTE_DEVTYPE_WHITELISTED_PCI \
+ _Pragma("GCC message \"'RTE_DEVTYPE_WHITELISTED' is deprecated\"") \
+ RTE_DEVTYPE_ALLOWLIST_PCI
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#199: FILE: lib/librte_eal/include/rte_devargs.h:41:
+#define RTE_DEVTYPE_BLACKLISTED_PCI \
+ _Pragma("GCC message \"'RTE_DEVTYPE_BLACKLISTED' is deprecated\"") \
+ RTE_DEVTYPE_BLOCKLIST_PCI
total: 6 errors, 0 warnings, 88 lines checked
parent reply other threads:[~2020-06-10 7:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200607170127.15694-5-stephen@networkplumber.org>]
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=20200610075626.7E9AD2BFA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stephen@networkplumber.org \
--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).