From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw97142 [PATCH] eal: remove the deprecated whitelist/blacklist and master/slave API's
Date: Fri, 20 Aug 2021 05:17:16 +0200 (CEST) [thread overview]
Message-ID: <20210820031716.36ABD122434@dpdk.org> (raw)
In-Reply-To: <20210820031614.451034-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/97142
_coding style issues_
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#62:
Subject: [dpdk-dev] [PATCH] eal: remove the deprecated whitelist/blacklist
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#62:
Subject: [dpdk-dev] [PATCH] eal: remove the deprecated whitelist/blacklist
WARNING:TYPO_SPELLING: 'compatiability' may be misspelled - perhaps 'compatibility'?
#78:
Remove the compatiability hooks that were added in 20.11 around
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#79:
master/slave and blacklist/whitelist.
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#79:
master/slave and blacklist/whitelist.
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#79:
master/slave and blacklist/whitelist.
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#79:
master/slave and blacklist/whitelist.
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#105: FILE: doc/guides/rel_notes/release_21_11.rst:71:
+* eal: Removed the deprecated function ``rte_get_master_lcore()``
WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#106: FILE: doc/guides/rel_notes/release_21_11.rst:72:
+ and the iterarator macro ``RTE_LCORE_FOREACH_SLAVE``.
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#109: FILE: doc/guides/rel_notes/release_21_11.rst:75:
+ blacklist/whitelist are removed. Users must use the new
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#109: FILE: doc/guides/rel_notes/release_21_11.rst:75:
+ blacklist/whitelist are removed. Users must use the new
total: 0 errors, 11 warnings, 152 lines checked
--- a/doc/guides/rel_notes/release_21_11.rst
+++ b/doc/guides/rel_notes/release_21_11.rst
next parent reply other threads:[~2021-08-20 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210820031614.451034-1-stephen@networkplumber.org>
2021-08-20 3:17 ` checkpatch [this message]
2021-08-20 3:58 ` [dpdk-test-report] |SUCCESS| pw97142 [dpdk-dev] " 0-day Robot
2021-08-20 3:37 [dpdk-test-report] |WARNING| pw97142 " dpdklab
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=20210820031716.36ABD122434@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).