automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw132222 [RFC] rte_ether_unformat: accept more inputs
Date: Fri, 29 Sep 2023 18:37:41 +0200 (CEST)	[thread overview]
Message-ID: <20230929163741.F065F120D36@dpdk.org> (raw)
In-Reply-To: <20230929163611.62691-1-stephen@networkplumber.org>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'seperated' may be misspelled - perhaps 'separated'?
#163: FILE: lib/net/rte_ether.c:103:
+ * Scan input to see if seperated by dash, colon or period

WARNING:TYPO_SPELLING: 'seperator' may be misspelled - perhaps 'separator'?
#164: FILE: lib/net/rte_ether.c:104:
+ * Returns seperator and number of matches

WARNING:TYPO_SPELLING: 'seperators' may be misspelled - perhaps 'separators'?
#165: FILE: lib/net/rte_ether.c:105:
+ * If seperators are mixed will return

WARNING:TYPO_SPELLING: 'seperators' may be misspelled - perhaps 'separators'?
#169: FILE: lib/net/rte_ether.c:109:
+	const char seperators[] = "-:.";

WARNING:STATIC_CONST_CHAR_ARRAY: const array should probably be static const
#169: FILE: lib/net/rte_ether.c:109:
+	const char seperators[] = "-:.";

WARNING:TYPO_SPELLING: 'seperators' may be misspelled - perhaps 'separators'?
#173: FILE: lib/net/rte_ether.c:113:
+	cp = strpbrk(s, seperators);

WARNING:TYPO_SPELLING: 'seperator' may be misspelled - perhaps 'separator'?
#180: FILE: lib/net/rte_ether.c:120:
+		/* find next instance of seperator */

WARNING:TYPO_SPELLING: 'seperated' may be misspelled - perhaps 'separated'?
#190: FILE: lib/net/rte_ether.c:130:
+ *  - Linux format six groups of hexadecimal digits seperated by colon

WARNING:TYPO_SPELLING: 'seperated' may be misspelled - perhaps 'separated'?
#191: FILE: lib/net/rte_ether.c:131:
+ *  - Windows format six groups seperated by hyphen

total: 0 errors, 9 warnings, 131 lines checked

      parent reply	other threads:[~2023-09-29 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230929163611.62691-1-stephen@networkplumber.org>
2023-09-29 16:17 ` |SUCCESS| " qemudev
2023-09-29 16:21 ` |FAILURE| " qemudev
2023-09-29 16:37 ` checkpatch [this message]

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=20230929163741.F065F120D36@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=stephen@networkplumber.org \
    --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).