automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: [dpdk-test-report] |WARNING| pw94361 [PATCH v3] app/testpmd: send failure logs to stderr
Date: Thu, 17 Jun 2021 16:22:35 +0200 (CEST)	[thread overview]
Message-ID: <20210617142235.43595122E3A@dpdk.org> (raw)
In-Reply-To: <20210617142026.1133460-1-andrew.rybchenko@oktetlabs.ru>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/94361

_coding style issues_


WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1309: FILE: app/test-pmd/cmdline.c:6182:
+		fprintf(stderr, "	Failed to get slave list for port = %d
",

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1320: FILE: app/test-pmd/cmdline.c:6202:
+			"	Failed to get active slave list for port = %d
",

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1330: FILE: app/test-pmd/cmdline.c:6220:
+		fprintf(stderr, "	Failed to get primary slave for port = %d
",

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1341: FILE: app/test-pmd/cmdline.c:6274:
+		fprintf(stderr, "	 Failed to set primary slave for port = %d.
",

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1342: FILE: app/test-pmd/cmdline.c:6275:
+			master_port_id);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1353: FILE: app/test-pmd/cmdline.c:6332:
+			"	 Failed to add slave %d to master port = %d.
",

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1353: FILE: app/test-pmd/cmdline.c:6332:
+			"	 Failed to add slave %d to master port = %d.
",

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1354: FILE: app/test-pmd/cmdline.c:6333:
+			slave_port_id, master_port_id);

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1354: FILE: app/test-pmd/cmdline.c:6333:
+			slave_port_id, master_port_id);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1365: FILE: app/test-pmd/cmdline.c:6391:
+			"	 Failed to remove slave %d from master port = %d.
",

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1365: FILE: app/test-pmd/cmdline.c:6391:
+			"	 Failed to remove slave %d from master port = %d.
",

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1366: FILE: app/test-pmd/cmdline.c:6392:
+			slave_port_id, master_port_id);

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1366: FILE: app/test-pmd/cmdline.c:6392:
+			slave_port_id, master_port_id);

WARNING:LONG_LINE: line length of 107 exceeds 100 columns
#3439: FILE: app/test-pmd/config.c:980:
+			"Port %d: register offset %u (0x%X) out of port PCI resource (length=%"PRIu64")
",

total: 0 errors, 14 warnings, 4811 lines checked
--- a/doc/guides/rel_notes/release_21_08.rst
+++ b/doc/guides/rel_notes/release_21_08.rst

       reply	other threads:[~2021-06-17 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210617142026.1133460-1-andrew.rybchenko@oktetlabs.ru>
2021-06-17 14:22 ` checkpatch [this message]
2021-06-17 16:01 ` [dpdk-test-report] |SUCCESS| pw94361 [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=20210617142235.43595122E3A@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --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).