From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "McDaniel, Timothy" <timothy.mcdaniel@intel.com>
Subject: [dpdk-test-report] |WARNING| pw75057 [PATCH 05/27] event/dlb: add DLB documentation
Date: Thu, 30 Jul 2020 21:55:58 +0200 (CEST) [thread overview]
Message-ID: <20200730195558.1484C1C030@dpdk.org> (raw)
In-Reply-To: <1596138614-17409-6-git-send-email-timothy.mcdaniel@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/75057
_coding style issues_
WARNING:TYPO_SPELLING: 'documen' may be misspelled - perhaps 'document'?
#48:
Subject: [dpdk-dev] =?utf-8?q?=5BPATCH_05/27=5D_event/dlb=3A_add_DLB_documen?=
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#117: FILE: doc/guides/eventdevs/dlb.rst:40:
+VAS Configuration
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#120: FILE: doc/guides/eventdevs/dlb.rst:43:
+A VAS is a scheduling domain, of which there are 32 in the DLB.
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#121: FILE: doc/guides/eventdevs/dlb.rst:44:
+When a VAS is configured, it allocates load-balanced and
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#122: FILE: doc/guides/eventdevs/dlb.rst:45:
+directed queues, ports, credits, and other hardware resources. Some VAS
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#125: FILE: doc/guides/eventdevs/dlb.rst:48:
+VAS), are not.
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#145: FILE: doc/guides/eventdevs/dlb.rst:68:
+When a VAS is created in ``rte_event_dev_configure()``, the user specifies
total: 0 errors, 7 warnings, 343 lines checked
parent reply other threads:[~2020-07-30 19:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1596138614-17409-6-git-send-email-timothy.mcdaniel@intel.com>]
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=20200730195558.1484C1C030@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=timothy.mcdaniel@intel.com \
/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).