From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw138283 [PATCH] test-pmd: add more packet decode options verbose
Date: Tue, 12 Mar 2024 23:03:15 +0100 (CET) [thread overview]
Message-ID: <20240312220315.CA1361223EF@dpdk.org> (raw)
In-Reply-To: <20240312220129.70667-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/138283
_coding style issues_
WARNING:TYPO_SPELLING: 'tha' may be misspelled - perhaps 'than'?
#266: FILE: app/test-pmd/util.c:338:
+ rte_ether_format_addr(buf, sizeof(buf), &arp->arp_data.arp_tha);
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
#328: FILE: app/test-pmd/util.c:400:
+#define PRINT_TCP_FLAG(flag) \
+ if (tcph->tcp_flags & RTE_TCP_ ## flag ## _FLAG) \
+ printf(" [" #flag" ]")
total: 1 errors, 1 warnings, 464 lines checked
Warning in app/test-pmd/util.c:
Using __atomic_xxx/__ATOMIC_XXX built-ins, prefer rte_atomic_xxx/rte_memory_order_xxx
next prev parent reply other threads:[~2024-03-12 22:03 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240312220129.70667-1-stephen@networkplumber.org>
2024-03-12 21:38 ` |SUCCESS| pw138283 [PATCH] test-pmd: add more packet decode options (verbose) qemudev
2024-03-12 21:42 ` qemudev
2024-03-12 22:03 ` checkpatch [this message]
2024-03-12 23:03 ` 0-day Robot
2024-03-12 23:13 ` |SUCCESS| pw138283 [PATCH] test-pmd: add more packet decode options dpdklab
2024-03-12 23:13 ` dpdklab
2024-03-12 23:15 ` dpdklab
2024-03-12 23:15 ` dpdklab
2024-03-12 23:16 ` dpdklab
2024-03-12 23:16 ` dpdklab
2024-03-12 23:24 ` dpdklab
2024-03-12 23:24 ` dpdklab
2024-03-12 23:31 ` dpdklab
2024-03-12 23:31 ` dpdklab
2024-03-12 23:32 ` dpdklab
2024-03-12 23:32 ` dpdklab
2024-03-12 23:33 ` dpdklab
2024-03-12 23:33 ` dpdklab
2024-03-12 23:33 ` dpdklab
2024-03-12 23:33 ` dpdklab
2024-03-12 23:33 ` dpdklab
2024-03-12 23:34 ` dpdklab
2024-03-12 23:34 ` dpdklab
2024-03-12 23:34 ` dpdklab
2024-03-12 23:35 ` dpdklab
2024-03-12 23:35 ` dpdklab
2024-03-12 23:35 ` dpdklab
2024-03-12 23:35 ` dpdklab
2024-03-12 23:36 ` dpdklab
2024-03-12 23:36 ` dpdklab
2024-03-12 23:36 ` dpdklab
2024-03-12 23:36 ` dpdklab
2024-03-12 23:36 ` dpdklab
2024-03-12 23:36 ` dpdklab
2024-03-12 23:37 ` dpdklab
2024-03-12 23:37 ` dpdklab
2024-03-12 23:37 ` dpdklab
2024-03-12 23:37 ` dpdklab
2024-03-12 23:37 ` dpdklab
2024-03-12 23:38 ` dpdklab
2024-03-12 23:38 ` dpdklab
2024-03-12 23:38 ` dpdklab
2024-03-12 23:38 ` dpdklab
2024-03-12 23:38 ` dpdklab
2024-03-12 23:38 ` dpdklab
2024-03-12 23:39 ` dpdklab
2024-03-12 23:39 ` dpdklab
2024-03-12 23:39 ` dpdklab
2024-03-12 23:40 ` dpdklab
2024-03-12 23:40 ` dpdklab
2024-03-12 23:41 ` dpdklab
2024-03-12 23:41 ` dpdklab
2024-03-12 23:41 ` dpdklab
2024-03-12 23:42 ` dpdklab
2024-03-12 23:43 ` dpdklab
2024-03-12 23:43 ` dpdklab
2024-03-12 23:44 ` dpdklab
2024-03-12 23:44 ` dpdklab
2024-03-12 23:45 ` dpdklab
2024-03-12 23:47 ` dpdklab
2024-03-12 23:49 ` dpdklab
2024-03-12 23:49 ` dpdklab
2024-03-12 23:52 ` dpdklab
2024-03-12 23:57 ` dpdklab
2024-03-13 0:31 ` dpdklab
2024-03-13 0:46 ` dpdklab
2024-03-13 0:48 ` |WARNING| " dpdklab
2024-03-13 0:49 ` |SUCCESS| " dpdklab
2024-03-13 1:00 ` dpdklab
2024-03-13 1:02 ` |WARNING| " dpdklab
2024-03-13 1:42 ` |SUCCESS| " dpdklab
2024-03-16 14:59 ` dpdklab
2024-03-16 15:35 ` dpdklab
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=20240312220315.CA1361223EF@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).