From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw80757 [PATCH v6 01/18] doc/coding_style: add policy about master/slave
Date: Wed, 14 Oct 2020 17:29:41 +0200 (CEST) [thread overview]
Message-ID: <20201014152941.832D61DDFA@dpdk.org> (raw)
In-Reply-To: <20201014152756.6518-2-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/80757
_coding style issues_
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#81:
introducing new master/slave usage. This is taken from the similar
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#81:
introducing new master/slave usage. This is taken from the similar
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#102: FILE: doc/guides/contributing/coding_style.rst:290:
+'master / slave' (or 'slave' independent of 'master') and 'blacklist /
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#102: FILE: doc/guides/contributing/coding_style.rst:290:
+'master / slave' (or 'slave' independent of 'master') and 'blacklist /
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#102: FILE: doc/guides/contributing/coding_style.rst:290:
+'master / slave' (or 'slave' independent of 'master') and 'blacklist /
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#102: FILE: doc/guides/contributing/coding_style.rst:290:
+'master / slave' (or 'slave' independent of 'master') and 'blacklist /
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#102: FILE: doc/guides/contributing/coding_style.rst:290:
+'master / slave' (or 'slave' independent of 'master') and 'blacklist /
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#103: FILE: doc/guides/contributing/coding_style.rst:291:
+whitelist' is not allowed.
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#105: FILE: doc/guides/contributing/coding_style.rst:293:
+Recommended replacements for 'master / slave' are:
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#105: FILE: doc/guides/contributing/coding_style.rst:293:
+Recommended replacements for 'master / slave' are:
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#112: FILE: doc/guides/contributing/coding_style.rst:300:
+Recommended replacements for 'blacklist/whitelist' are:
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#112: FILE: doc/guides/contributing/coding_style.rst:300:
+Recommended replacements for 'blacklist/whitelist' are:
WARNING:TYPO_SPELLING: 'compatability' may be misspelled - perhaps 'compatibility'?
#116: FILE: doc/guides/contributing/coding_style.rst:304:
+Exceptions for introducing new usage is to maintain compatability
total: 0 errors, 13 warnings, 29 lines checked
parent reply other threads:[~2020-10-14 15:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201014152756.6518-2-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=20201014152941.832D61DDFA@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).