From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw74875 [PATCH 20.08 4/6] doc: announce deprecation blacklist/whitelist
Date: Mon, 27 Jul 2020 21:21:50 +0200 (CEST) [thread overview]
Message-ID: <20200727192150.9455D1BFE0@dpdk.org> (raw)
In-Reply-To: <20200727192015.26418-5-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/74875
_coding style issues_
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#81:
Announce upcoming changes for 20.11 around the terms blacklist
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#82:
and whitelist.
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#98: FILE: doc/guides/rel_notes/deprecation.rst:169:
+* eal: The terms blacklist and whitelist to describe devices used
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#98: FILE: doc/guides/rel_notes/deprecation.rst:169:
+* eal: The terms blacklist and whitelist to describe devices used
WARNING:TYPO_SPELLING: 'relase' may be misspelled - perhaps 'release'?
#99: FILE: doc/guides/rel_notes/deprecation.rst:170:
+ by DPDK will be replaced by blocked and allowed in the 20.11 relase.
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#109: FILE: doc/guides/rel_notes/deprecation.rst:180:
+ ``-b, --pci-blacklist`` to ``-x, --exclude`` and
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#110: FILE: doc/guides/rel_notes/deprecation.rst:181:
+ ``-w, --pci-whitelist`` to ``-i, --include``.
total: 0 errors, 7 warnings, 19 lines checked
parent reply other threads:[~2020-07-27 19:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200727192015.26418-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=20200727192150.9455D1BFE0@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).