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| pw142652 [PATCH v2 1/3] net: add new packet dissector
Date: Tue, 23 Jul 2024 04:47:19 +0200 (CEST)	[thread overview]
Message-ID: <20240723024719.A8EA1127EE2@dpdk.org> (raw)
In-Reply-To: <20240723024537.980016-2-stephen@networkplumber.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

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

_coding style issues_


WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#139: FILE: lib/net/rte_dissect.c:9:
+#include <stdio.h>

WARNING:TYPO_SPELLING: 'tha' may be misspelled - perhaps 'than'?
#211: FILE: lib/net/rte_dissect.c:81:
+		rte_ether_format_addr(buf, sizeof(buf), &arp->arp_data.arp_tha);

WARNING:LONG_LINE: line length of 103 exceeds 100 columns
#268: FILE: lib/net/rte_dissect.c:138:
+		fprintf(f, "UDP %u %u → %u ", rte_be_to_cpu_16(udph->dgram_len), src_port, dst_port);

ERROR:MULTISTATEMENT_MACRO_USE_DO_WHILE: Macros starting with if should be enclosed by a do - while loop to avoid possible if/else logic defects
#290: FILE: lib/net/rte_dissect.c:160:
+#define PRINT_TCP_FLAG(flag) \
+	if (tcph->tcp_flags & RTE_TCP_ ## flag ## _FLAG) \
+		fprintf(f, " [" #flag" ]")

WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#505: FILE: lib/net/rte_dissect.h:12:
+#include <stdio.h>

total: 1 errors, 4 warnings, 421 lines checked

           reply	other threads:[~2024-07-23  2:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20240723024537.980016-2-stephen@networkplumber.org>]

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=20240723024719.A8EA1127EE2@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).