From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Henry Nadeau <hnadeau@iol.unh.edu>
Subject: [dpdk-test-report] |WARNING| pw96296 [PATCH v3] doc: spell check
Date: Mon, 26 Jul 2021 18:37:39 +0200 (CEST) [thread overview]
Message-ID: <20210726163739.D5FC0122E58@dpdk.org> (raw)
In-Reply-To: <20210726163710.39392-1-hnadeau@iol.unh.edu>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/96296
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#76:
Implimenting automatic documentation spell checking, fixed any spelling errors that were picked up by the spell checker. If any of these corrections are incorrect please let me know so I can update the spell checker.
WARNING:TYPO_SPELLING: 'Implimenting' may be misspelled - perhaps 'Implementing'?
#76:
Implimenting automatic documentation spell checking, fixed any spelling errors that were picked up by the spell checker. If any of these corrections are incorrect please let me know so I can update the spell checker.
WARNING:TYPO_SPELLING: 'preform' may be misspelled - perhaps 'perform'?
#324: FILE: doc/guides/prog_guide/bbdev.rst:642:
+ "iter_max","maximum number of iterations to preform in decode all CBs"
total: 0 errors, 3 warnings, 327 lines checked
--- a/doc/guides/rel_notes/release_16_11.rst
+++ b/doc/guides/rel_notes/release_16_11.rst
--- a/doc/guides/rel_notes/release_19_08.rst
+++ b/doc/guides/rel_notes/release_19_08.rst
--- a/doc/guides/rel_notes/release_21_08.rst
+++ b/doc/guides/rel_notes/release_21_08.rst
--- a/doc/guides/rel_notes/release_2_2.rst
+++ b/doc/guides/rel_notes/release_2_2.rst
next parent reply other threads:[~2021-07-26 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210726163710.39392-1-hnadeau@iol.unh.edu>
2021-07-26 16:37 ` checkpatch [this message]
2021-07-26 17:06 ` [dpdk-test-report] |SUCCESS| pw96296 [dpdk-dev] " 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=20210726163739.D5FC0122E58@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=hnadeau@iol.unh.edu \
--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).