From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw73980 [PATCH v4 04/11] eal: replace usage of blacklist/whitelist in enum
Date: Tue, 14 Jul 2020 07:41:14 +0200 (CEST) [thread overview]
Message-ID: <20200714054114.15E271D165@dpdk.org> (raw)
In-Reply-To: <20200714053919.5609-5-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/73980
_coding style issues_
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#82:
The terms blacklist and whitelist are often seen as reminders
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#82:
The terms blacklist and whitelist are often seen as reminders
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#90:
The old names relating to blacklist and whitelist are replaced
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#90:
The old names relating to blacklist and whitelist are replaced
WARNING:TYPO_SPELLING: 'WHITELIST' may be misspelled - perhaps 'ALLOWLIST'?
#153: FILE: lib/librte_eal/include/rte_bus.h:223:
+#define RTE_BUS_SCAN_WHITELIST RTE_BUS_SCAN_ALLOWLIST
WARNING:TYPO_SPELLING: 'BLACKLIST' may be misspelled - perhaps 'BLOCKLIST'?
#154: FILE: lib/librte_eal/include/rte_bus.h:224:
+#define RTE_BUS_SCAN_BLACKLIST RTE_BUS_SCAN_BLOCKLIST
WARNING:TYPO_SPELLING: 'compatiablity' may be misspelled - perhaps 'compatibility'?
#173: FILE: lib/librte_eal/include/rte_dev.h:77:
+/* Backwards compatiablity will be deprecated */
WARNING:TYPO_SPELLING: 'compatiablity' may be misspelled - perhaps 'compatibility'?
#195: FILE: lib/librte_eal/include/rte_devargs.h:37:
+/* Backwards compatiablity will be removed later */
total: 0 errors, 8 warnings, 76 lines checked
parent reply other threads:[~2020-07-14 5:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200714053919.5609-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=20200714054114.15E271D165@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).