From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw83929 [PATCH v10 7/7] eal: mark old definitions as deprecated
Date: Tue, 10 Nov 2020 23:59:01 +0100 (CET) [thread overview]
Message-ID: <20201110225901.4D7635A51@dpdk.org> (raw)
In-Reply-To: <20201110225544.1876-8-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/83929
_coding style issues_
WARNING:TYPO_SPELLING: 'compatiablity' may be misspelled - perhaps 'compatibility'?
#80:
This patch marks the compatiablity macros with RTE_DEPRECATED
WARNING:TYPO_SPELLING: 'WHITELIST' may be misspelled - perhaps 'ALLOWLIST'?
#101: 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
#101: 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'?
#102: 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'?
#103: 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
#103: 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'?
#104: 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
#118: 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
#120: 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
#135: 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
#137: 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, 5 warnings, 36 lines checked
next parent reply other threads:[~2020-11-10 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201110225544.1876-8-stephen@networkplumber.org>
2020-11-10 22:59 ` checkpatch [this message]
2020-11-11 1:27 ` [dpdk-test-report] |SUCCESS| pw83929 " 0-day Robot
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=20201110225901.4D7635A51@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).