From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw81613 [PATCH v2 5/5] doc: change references to blacklist and whitelist
Date: Tue, 20 Oct 2020 18:23:06 +0200 (CEST) [thread overview]
Message-ID: <20201020162306.E9C5CA24B@dpdk.org> (raw)
In-Reply-To: <20201020162018.10058-6-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/81613
_coding style issues_
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#65:
Subject: [dpdk-dev] [PATCH v2 5/5] doc: change references to blacklist and
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#82:
The first was use of whitelist when describing address
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#85:
The other is the legacy -w whitelist option for PCI
WARNING:BAD_SIGN_OFF: Duplicate signature
#95:
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#279: FILE: doc/guides/eventdevs/octeontx2.rst:110:
+ -a 0002:0e:00.0,tim_disable_npa=1
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#288: FILE: doc/guides/eventdevs/octeontx2.rst:121:
+ -a 0002:0e:00.0,tim_chnk_slots=1023
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#297: FILE: doc/guides/eventdevs/octeontx2.rst:129:
+ -a 0002:0e:00.0,tim_stats_ena=1
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#306: FILE: doc/guides/eventdevs/octeontx2.rst:139:
+ -a 0002:0e:00.0,tim_rings_lmt=5
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#315: FILE: doc/guides/eventdevs/octeontx2.rst:149:
+ -a 0002:0e:00.0,tim_ring_ctl=[2-1023-1-0]
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#1168: FILE: doc/guides/rel_notes/release_20_11.rst:543:
+ has been changed from blacklist/whitelist to include/exclude.
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#1168: FILE: doc/guides/rel_notes/release_20_11.rst:543:
+ has been changed from blacklist/whitelist to include/exclude.
total: 0 errors, 11 warnings, 997 lines checked
next parent reply other threads:[~2020-10-20 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201020162018.10058-6-stephen@networkplumber.org>
2020-10-20 16:23 ` checkpatch [this message]
2020-10-20 20:29 ` [dpdk-test-report] |WARNING| pw81613 " 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=20201020162306.E9C5CA24B@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).