From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw83928 [PATCH v10 4/7] doc: update documentation to reflect new options
Date: Tue, 10 Nov 2020 23:58:59 +0100 (CET) [thread overview]
Message-ID: <20201110225859.7E06A5A0F@dpdk.org> (raw)
In-Reply-To: <20201110225544.1876-5-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/83928
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#263: FILE: doc/guides/eventdevs/octeontx2.rst:99:
+ -a 0002:0e:00.0,tim_disable_npa=1
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#272: FILE: doc/guides/eventdevs/octeontx2.rst:110:
+ -a 0002:0e:00.0,tim_chnk_slots=1023
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#281: FILE: doc/guides/eventdevs/octeontx2.rst:118:
+ -a 0002:0e:00.0,tim_stats_ena=1
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#290: FILE: doc/guides/eventdevs/octeontx2.rst:128:
+ -a 0002:0e:00.0,tim_rings_lmt=5
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#299: FILE: doc/guides/eventdevs/octeontx2.rst:138:
+ -a 0002:0e:00.0,tim_ring_ctl=[2-1023-1-0]
WARNING:TYPO_SPELLING: 'blacklist' may be misspelled - perhaps 'blocklist'?
#1201: FILE: doc/guides/rel_notes/release_20_11.rst:648:
+ has been changed from blacklist/whitelist to block/allow list.
WARNING:TYPO_SPELLING: 'whitelist' may be misspelled - perhaps 'allowlist'?
#1201: FILE: doc/guides/rel_notes/release_20_11.rst:648:
+ has been changed from blacklist/whitelist to block/allow list.
total: 0 errors, 7 warnings, 1047 lines checked
parent reply other threads:[~2020-11-10 22:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201110225544.1876-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=20201110225859.7E06A5A0F@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).