From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Subject: [dpdk-test-report] |WARNING| pw76969 [PATCH v3 36/41] examples/pipeline: add new example application
Date: Wed, 9 Sep 2020 01:58:48 +0200 (CEST) [thread overview]
Message-ID: <20200908235848.810A61BE0C@dpdk.org> (raw)
In-Reply-To: <20200908201830.74206-37-cristian.dumitrescu@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/76969
_coding style issues_
WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#204: FILE: examples/pipeline/main.c:47:
+ SKIP_MASTER);
ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#207: FILE: examples/pipeline/main.c:50:
+ for ( ; ; );
WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#884: FILE: examples/pipeline/thread.c:34:
+ * Master thead: data plane thread context
WARNING:TYPO_SPELLING: 'thead' may be misspelled - perhaps 'thread'?
#884: FILE: examples/pipeline/thread.c:34:
+ * Master thead: data plane thread context
WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#919: FILE: examples/pipeline/thread.c:69:
+ * Master thread: data plane thread init
WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#946: FILE: examples/pipeline/thread.c:96:
+ RTE_LCORE_FOREACH_SLAVE(i) {
WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#978: FILE: examples/pipeline/thread.c:128:
+ /* Master thread records */
WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#1006: FILE: examples/pipeline/thread.c:156:
+ * Master thread & data plane threads: message passing
WARNING:TYPO_SPELLING: 'Master' may be misspelled - perhaps 'Primary'?
#1034: FILE: examples/pipeline/thread.c:184:
+ * Master thread
total: 1 errors, 8 warnings, 1304 lines checked
parent reply other threads:[~2020-09-08 23:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200908201830.74206-37-cristian.dumitrescu@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=20200908235848.810A61BE0C@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=cristian.dumitrescu@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).