From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bingbin Chen <chen.bingbin@zte.com.cn>
Subject: |WARNING| pw154519 [PATCH v1 2/2] net/zxdh: add support flow director ops
Date: Tue, 17 Jun 2025 11:39:37 +0200 (CEST) [thread overview]
Message-ID: <20250617093937.3D3291252C7@dpdk.org> (raw)
In-Reply-To: <20250617093256.3570516-1-chen.bingbin@zte.com.cn>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/154519
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#58:
Provide support for ETH, VLAN, IPv4/IPv6, TCP/UDP, VXLAN, and mask matching,
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#335: FILE: drivers/net/zxdh/zxdh_flow.c:6:
+#include <stdio.h>
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'buf_size' - possible side-effects?
#376: FILE: drivers/net/zxdh/zxdh_flow.c:47:
+#define MKDUMPSTR(buf, buf_size, cur_len, ...) \
+do { \
+ if ((cur_len) >= (buf_size)) \
+ break; \
+ (cur_len) += snprintf((buf) + (cur_len), (buf_size) - (cur_len), __VA_ARGS__); \
+} while (0)
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'cur_len' - possible side-effects?
#376: FILE: drivers/net/zxdh/zxdh_flow.c:47:
+#define MKDUMPSTR(buf, buf_size, cur_len, ...) \
+do { \
+ if ((cur_len) >= (buf_size)) \
+ break; \
+ (cur_len) += snprintf((buf) + (cur_len), (buf_size) - (cur_len), __VA_ARGS__); \
+} while (0)
CHECK:CAMELCASE: Avoid CamelCase: <IPv6_BYTES_FMT>
#454: FILE: drivers/net/zxdh/zxdh_flow.c:125:
+ "L3 dstip=0x%08x 0x%08x 0x%08x 0x%08x("IPv6_BYTES_FMT")
",
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#454: FILE: drivers/net/zxdh/zxdh_flow.c:125:
+ "L3 dstip=0x%08x 0x%08x 0x%08x 0x%08x("IPv6_BYTES_FMT")
",
CHECK:CAMELCASE: Avoid CamelCase: <IPv6_BYTES>
#458: FILE: drivers/net/zxdh/zxdh_flow.c:129:
+ IPv6_BYTES(key->dst_ip));
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#460: FILE: drivers/net/zxdh/zxdh_flow.c:131:
+ " srcip=0x%08x 0x%08x 0x%08x 0x%08x("IPv6_BYTES_FMT")
",
WARNING:TYPO_SPELLING: 'realease' may be misspelled - perhaps 'release'?
#1233: FILE: drivers/net/zxdh/zxdh_flow.c:904:
+ "realease handle_idx to hw failed");
WARNING:TYPO_SPELLING: 'realease' may be misspelled - perhaps 'release'?
#1424: FILE: drivers/net/zxdh/zxdh_flow.c:1095:
+ "realease handle_idx to hw failed");
WARNING:TYPO_SPELLING: 'realease' may be misspelled - perhaps 'release'?
#1427: FILE: drivers/net/zxdh/zxdh_flow.c:1098:
+ PMD_DRV_LOG(DEBUG, "realease handle_idx to hw succ! %d", handle_idx);
ERROR:C99_COMMENTS: do not use C99 // comments
#1618: FILE: drivers/net/zxdh/zxdh_flow.c:1289:
+ //ether_type = rte_be_to_cpu_16(eth_spec->type);
CHECK:CAMELCASE: Avoid CamelCase: <IPv4_BYTES>
#2371: FILE: drivers/net/zxdh/zxdh_flow.h:32:
+#ifndef IPv4_BYTES
CHECK:CAMELCASE: Avoid CamelCase: <IPv4_BYTES_FMT>
#2372: FILE: drivers/net/zxdh/zxdh_flow.h:33:
+#define IPv4_BYTES_FMT "%" PRIu8 ".%" PRIu8 ".%" PRIu8 ".%" PRIu8
CHECK:CAMELCASE: Avoid CamelCase: <PRIu8>
#2372: FILE: drivers/net/zxdh/zxdh_flow.h:33:
+#define IPv4_BYTES_FMT "%" PRIu8 ".%" PRIu8 ".%" PRIu8 ".%" PRIu8
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#2373: FILE: drivers/net/zxdh/zxdh_flow.h:34:
+#define IPv4_BYTES(addr) \
+ (uint8_t)(((addr) >> 24) & 0xFF),\
+ (uint8_t)(((addr) >> 16) & 0xFF),\
+ (uint8_t)(((addr) >> 8) & 0xFF),\
+ (uint8_t)((addr) & 0xFF)
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'addr' - possible side-effects?
#2373: FILE: drivers/net/zxdh/zxdh_flow.h:34:
+#define IPv4_BYTES(addr) \
+ (uint8_t)(((addr) >> 24) & 0xFF),\
+ (uint8_t)(((addr) >> 16) & 0xFF),\
+ (uint8_t)(((addr) >> 8) & 0xFF),\
+ (uint8_t)((addr) & 0xFF)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#2383: FILE: drivers/net/zxdh/zxdh_flow.h:44:
+#define IPv6_BYTES(addr) \
+ addr[0], addr[1], addr[2], addr[3], addr[4], addr[5], addr[6], addr[7], \
+ addr[8], addr[9], addr[10], addr[11], addr[12], addr[13], addr[14], addr[15]
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'addr' - possible side-effects?
#2383: FILE: drivers/net/zxdh/zxdh_flow.h:44:
+#define IPv6_BYTES(addr) \
+ addr[0], addr[1], addr[2], addr[3], addr[4], addr[5], addr[6], addr[7], \
+ addr[8], addr[9], addr[10], addr[11], addr[12], addr[13], addr[14], addr[15]
total: 3 errors, 5 warnings, 11 checks, 3014 lines checked
next prev parent reply other threads:[~2025-06-17 9:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250617093256.3570516-1-chen.bingbin@zte.com.cn>
2025-06-17 9:05 ` |SUCCESS| pw154518-154519 " qemudev
2025-06-17 9:09 ` qemudev
2025-06-17 9:39 ` checkpatch [this message]
2025-06-17 10:59 ` |SUCCESS| pw154518-154519 [PATCH] [v1,2/2] net/zxdh: add support flo dpdklab
2025-06-17 11:07 ` dpdklab
2025-06-17 11:10 ` dpdklab
2025-06-17 11:11 ` |SUCCESS| pw154519 [PATCH v1 2/2] net/zxdh: add support flow director ops 0-day Robot
2025-06-17 11:15 ` |SUCCESS| pw154518-154519 [PATCH] [v1,2/2] net/zxdh: add support flo dpdklab
2025-06-17 11:21 ` |PENDING| " dpdklab
2025-06-17 11:22 ` dpdklab
2025-06-17 11:35 ` |SUCCESS| " dpdklab
2025-06-17 11:36 ` |FAILURE| " dpdklab
2025-06-17 11:36 ` dpdklab
2025-06-17 11:44 ` dpdklab
2025-06-17 11:53 ` |SUCCESS| " dpdklab
2025-06-17 12:00 ` dpdklab
2025-06-17 12:01 ` |FAILURE| " dpdklab
2025-06-17 12:10 ` |SUCCESS| " dpdklab
2025-06-17 13:51 ` dpdklab
2025-06-17 18:02 ` dpdklab
2025-06-17 18:37 ` |PENDING| " dpdklab
2025-06-17 18:56 ` |FAILURE| " 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=20250617093937.3D3291252C7@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=chen.bingbin@zte.com.cn \
--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).