From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw81797 [PATCH v3 1/5] eal: replace usage of blacklist/whitelist in enum
Date: Thu, 22 Oct 2020 16:40:12 +0200 (CEST) [thread overview]
Message-ID: <20201022144012.5BA6FAC4E@dpdk.org> (raw)
In-Reply-To: <20201022143925.30980-2-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/81797
_coding style issues_
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#64:
Subject: [dpdk-dev] [PATCH v3 1/5] eal: replace usage of blacklist/whitelist
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#64:
Subject: [dpdk-dev] [PATCH v3 1/5] eal: replace usage of blacklist/whitelist
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#84:
The old names relating to blacklist and whitelist are replaced
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#84:
The old names relating to blacklist and whitelist are replaced
WARNING:TYPO_SPELLING: 'WHITELIST' may be misspelled - perhaps 'ALLOWLIST'?
#147: FILE: lib/librte_eal/include/rte_bus.h:223:
+#define RTE_BUS_SCAN_WHITELIST \
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#147: FILE: lib/librte_eal/include/rte_bus.h:223:
+#define RTE_BUS_SCAN_WHITELIST \
+ RTE_DEPRECATED(RTE_BUS_SCAN_WHITELIST) RTE_BUS_SCAN_ALLOWLIST
WARNING:TYPO_SPELLING: 'WHITELIST' may be misspelled - perhaps 'ALLOWLIST'?
#148: FILE: lib/librte_eal/include/rte_bus.h:224:
+ RTE_DEPRECATED(RTE_BUS_SCAN_WHITELIST) RTE_BUS_SCAN_ALLOWLIST
WARNING:TYPO_SPELLING: 'BLACKLIST' may be misspelled - perhaps 'BLOCKLIST'?
#149: FILE: lib/librte_eal/include/rte_bus.h:225:
+#define RTE_BUS_SCAN_BLACKLIST \
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#149: FILE: lib/librte_eal/include/rte_bus.h:225:
+#define RTE_BUS_SCAN_BLACKLIST \
+ RTE_DEPRECATED(RTE_BUS_SCAN_BLACKLIST) RTE_BUS_SCAN_BLOCKLIST
WARNING:TYPO_SPELLING: 'BLACKLIST' may be misspelled - perhaps 'BLOCKLIST'?
#150: FILE: lib/librte_eal/include/rte_bus.h:226:
+ RTE_DEPRECATED(RTE_BUS_SCAN_BLACKLIST) RTE_BUS_SCAN_BLOCKLIST
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#170: FILE: lib/librte_eal/include/rte_dev.h:60:
+#define RTE_DEV_WHITELISTED \
+ RTE_DEPRECATED(RTE_DEV_WHITELISTED) RTE_DEV_ALLOWED
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#172: FILE: lib/librte_eal/include/rte_dev.h:62:
+#define RTE_DEV_BLACKLISTED \
+ RTE_DEPRECATED(RTE_DEV_BLACKLISTED) RTE_DEV_BLOCKED
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#194: FILE: lib/librte_eal/include/rte_devargs.h:38:
+#define RTE_DEVTYPE_WHITELISTED_PCI \
+ RTE_DEPRECATED(RTE_DEVTYPE_WHITELISTED_PCI) RTE_DEVTYPE_ALLOWED
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#196: FILE: lib/librte_eal/include/rte_devargs.h:40:
+#define RTE_DEVTYPE_BLACKLISTED_PCI \
+ RTE_DEPRECATED(RTE_DEVTYPE_BLACKLISTED_PCI) RTE_DEVTYPE_BLOCKED
total: 6 errors, 8 warnings, 82 lines checked
parent reply other threads:[~2020-10-22 14:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201022143925.30980-2-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=20201022144012.5BA6FAC4E@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).