From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nicolas Chautru <nicolas.chautru@intel.com>
Subject: |WARNING| pw122223 [PATCH v1 6/6] doc: updated naming convention for acc200 PMD
Date: Tue, 17 Jan 2023 23:41:06 +0100 (CET) [thread overview]
Message-ID: <20230117224106.1A72F123659@dpdk.org> (raw)
In-Reply-To: <20230117223642.17618-7-nicolas.chautru@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/122223
_coding style issues_
WARNING:TYPO_SPELLING: 'prevously' may be misspelled - perhaps 'previously'?
#177: FILE: doc/guides/bbdevs/vrb1.rst:256:
+prevously to refer to VRB1):
total: 0 errors, 1 warnings, 83 lines checked
next parent reply other threads:[~2023-01-17 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230117223642.17618-7-nicolas.chautru@intel.com>
2023-01-17 22:41 ` checkpatch [this message]
2023-01-17 23:03 ` |SUCCESS| pw122219-122223 " qemudev
2023-01-17 23:07 ` qemudev
2023-01-17 23:39 ` |FAILURE| pw122223 " 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=20230117224106.1A72F123659@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=nicolas.chautru@intel.com \
--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).