From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw83774 [PATCH v9 3/6] eal: replace pci-whitelist/pci-blacklist options
Date: Thu, 5 Nov 2020 23:38:16 +0100 (CET) [thread overview]
Message-ID: <20201105223816.6A141137D@dpdk.org> (raw)
In-Reply-To: <20201105223602.5965-4-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/83774
_coding style issues_
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#66:
Subject: [dpdk-dev] [PATCH v9 3/6] eal: replace pci-whitelist/pci-blacklist
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#66:
Subject: [dpdk-dev] [PATCH v9 3/6] eal: replace pci-whitelist/pci-blacklist
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#82:
Replace -w / --pci-whitelist with -a / --allow options
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#83:
and --pci-blacklist with --block.
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#115: FILE: lib/librte_eal/common/eal_common_options.c:67:
+ "w:" /* pci-whitelist (deprecated) */
WARNING:TYPO_SPELLING: 'BLACKLIST' may be misspelled - perhaps 'BLOCKLIST'?
#136: FILE: lib/librte_eal/common/eal_common_options.c:111:
+ {OPT_PCI_BLACKLIST, 1, NULL, OPT_PCI_BLACKLIST_NUM },
WARNING:TYPO_SPELLING: 'BLACKLIST' may be misspelled - perhaps 'BLOCKLIST'?
#136: FILE: lib/librte_eal/common/eal_common_options.c:111:
+ {OPT_PCI_BLACKLIST, 1, NULL, OPT_PCI_BLACKLIST_NUM },
WARNING:TYPO_SPELLING: 'WHITELIST' may be misspelled - perhaps 'ALLOWLIST'?
#137: FILE: lib/librte_eal/common/eal_common_options.c:112:
+ {OPT_PCI_WHITELIST, 1, NULL, OPT_PCI_WHITELIST_NUM },
WARNING:TYPO_SPELLING: 'WHITELIST' may be misspelled - perhaps 'ALLOWLIST'?
#137: FILE: lib/librte_eal/common/eal_common_options.c:112:
+ {OPT_PCI_WHITELIST, 1, NULL, OPT_PCI_WHITELIST_NUM },
WARNING:TYPO_SPELLING: 'BLACKLIST' may be misspelled - perhaps 'BLOCKLIST'?
#151: FILE: lib/librte_eal/common/eal_common_options.c:1460:
+ case OPT_PCI_BLACKLIST_NUM:
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#153: FILE: lib/librte_eal/common/eal_common_options.c:1462:
+ "Option --pci-blacklist is deprecated, use -b, --block instead
");
WARNING:BRACES: braces {} are not necessary for single statement blocks
#163: FILE: lib/librte_eal/common/eal_common_options.c:1468:
+ if (eal_option_device_add(RTE_DEVTYPE_BLOCKED, optarg) < 0) {
return -1;
}
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#172: FILE: lib/librte_eal/common/eal_common_options.c:1476:
+ "Option -w, --pci-whitelist is deprecated, use -a, --allow option instead
");
WARNING:BRACES: braces {} are not necessary for single statement blocks
#181: FILE: lib/librte_eal/common/eal_common_options.c:1482:
+ if (eal_option_device_add(RTE_DEVTYPE_ALLOWED, optarg) < 0) {
return -1;
}
WARNING:TYPO_SPELLING: 'BLACKLIST' may be misspelled - perhaps 'BLOCKLIST'?
#251: FILE: lib/librte_eal/common/eal_options.h:98:
+#define OPT_PCI_BLACKLIST "pci-blacklist"
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#251: FILE: lib/librte_eal/common/eal_options.h:98:
+#define OPT_PCI_BLACKLIST "pci-blacklist"
WARNING:TYPO_SPELLING: 'BLACKLIST' may be misspelled - perhaps 'BLOCKLIST'?
#252: FILE: lib/librte_eal/common/eal_options.h:99:
+ OPT_PCI_BLACKLIST_NUM,
total: 0 errors, 17 warnings, 144 lines checked
parent reply other threads:[~2020-11-05 22:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201105223602.5965-4-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=20201105223816.6A141137D@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).