From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <changqing.li@windriver.com>
Subject: |WARNING| pw153072 [PATCH] ethdev_trace.h: Update the trace point function when _TIME_BITS=64
Date: Tue, 22 Apr 2025 13:35:18 +0200 (CEST) [thread overview]
Message-ID: <20250422113518.E83C5123FA7@dpdk.org> (raw)
In-Reply-To: <20250422113523.867473-1-changqing.li@windriver.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153072
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#81:
498 | #define RTE_BUILD_BUG_ON(condition) ((void)sizeof(char[1 - 2*!!(condition)]))
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#111: FILE: lib/ethdev/ethdev_trace.h:1131:
+ rte_eth_trace_timesync_write_time,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#112: FILE: lib/ethdev/ethdev_trace.h:1132:
+ RTE_TRACE_POINT_ARGS(uint16_t port_id, const struct timespec *time,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#113: FILE: lib/ethdev/ethdev_trace.h:1133:
+ int ret),$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#113: FILE: lib/ethdev/ethdev_trace.h:1133:
+ int ret),$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#114: FILE: lib/ethdev/ethdev_trace.h:1134:
+ rte_trace_point_emit_u16(port_id);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#115: FILE: lib/ethdev/ethdev_trace.h:1135:
+ rte_trace_point_emit_size_t(time->tv_sec);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#116: FILE: lib/ethdev/ethdev_trace.h:1136:
+ rte_trace_point_emit_long(time->tv_nsec);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#117: FILE: lib/ethdev/ethdev_trace.h:1137:
+ rte_trace_point_emit_int(ret);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#141: FILE: lib/ethdev/ethdev_trace.h:2174:
+ rte_eth_trace_timesync_read_rx_timestamp,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#142: FILE: lib/ethdev/ethdev_trace.h:2175:
+ RTE_TRACE_POINT_ARGS(uint16_t port_id, const struct timespec *timestamp,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#143: FILE: lib/ethdev/ethdev_trace.h:2176:
+ uint32_t flags, int ret),$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#143: FILE: lib/ethdev/ethdev_trace.h:2176:
+ uint32_t flags, int ret),$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#144: FILE: lib/ethdev/ethdev_trace.h:2177:
+ rte_trace_point_emit_u16(port_id);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#145: FILE: lib/ethdev/ethdev_trace.h:2178:
+ rte_trace_point_emit_size_t(timestamp->tv_sec);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#146: FILE: lib/ethdev/ethdev_trace.h:2179:
+ rte_trace_point_emit_long(timestamp->tv_nsec);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#147: FILE: lib/ethdev/ethdev_trace.h:2180:
+ rte_trace_point_emit_u32(flags);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#148: FILE: lib/ethdev/ethdev_trace.h:2181:
+ rte_trace_point_emit_int(ret);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#166: FILE: lib/ethdev/ethdev_trace.h:2198:
+ rte_eth_trace_timesync_read_tx_timestamp,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#167: FILE: lib/ethdev/ethdev_trace.h:2199:
+ RTE_TRACE_POINT_ARGS(uint16_t port_id, const struct timespec *timestamp,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#168: FILE: lib/ethdev/ethdev_trace.h:2200:
+ int ret),$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#168: FILE: lib/ethdev/ethdev_trace.h:2200:
+ int ret),$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#169: FILE: lib/ethdev/ethdev_trace.h:2201:
+ rte_trace_point_emit_u16(port_id);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#170: FILE: lib/ethdev/ethdev_trace.h:2202:
+ rte_trace_point_emit_size_t(timestamp->tv_sec);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#171: FILE: lib/ethdev/ethdev_trace.h:2203:
+ rte_trace_point_emit_long(timestamp->tv_nsec);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#172: FILE: lib/ethdev/ethdev_trace.h:2204:
+ rte_trace_point_emit_int(ret);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#190: FILE: lib/ethdev/ethdev_trace.h:2221:
+ rte_eth_trace_timesync_read_time,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#191: FILE: lib/ethdev/ethdev_trace.h:2222:
+ RTE_TRACE_POINT_ARGS(uint16_t port_id, const struct timespec *time,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#192: FILE: lib/ethdev/ethdev_trace.h:2223:
+ int ret),$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#192: FILE: lib/ethdev/ethdev_trace.h:2223:
+ int ret),$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#193: FILE: lib/ethdev/ethdev_trace.h:2224:
+ rte_trace_point_emit_u16(port_id);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#194: FILE: lib/ethdev/ethdev_trace.h:2225:
+ rte_trace_point_emit_size_t(time->tv_sec);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#195: FILE: lib/ethdev/ethdev_trace.h:2226:
+ rte_trace_point_emit_long(time->tv_nsec);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#196: FILE: lib/ethdev/ethdev_trace.h:2227:
+ rte_trace_point_emit_int(ret);$
total: 4 errors, 30 warnings, 106 lines checked
next prev parent reply other threads:[~2025-04-22 11:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250422113523.867473-1-changqing.li@windriver.com>
2025-04-22 11:13 ` |SUCCESS| " qemudev
2025-04-22 11:17 ` qemudev
2025-04-22 11:35 ` checkpatch [this message]
2025-04-22 12:08 ` |SUCCESS| pw153072 [PATCH] ethdev_trace.h: Update the trace point fu dpdklab
2025-04-22 12:18 ` |PENDING| " dpdklab
2025-04-22 12:19 ` |SUCCESS| " dpdklab
2025-04-22 12:22 ` dpdklab
2025-04-22 12:25 ` |PENDING| " dpdklab
2025-04-22 12:29 ` |SUCCESS| " dpdklab
2025-04-22 12:30 ` |PENDING| " dpdklab
2025-04-22 12:33 ` |SUCCESS| " dpdklab
2025-04-22 12:35 ` dpdklab
2025-04-22 12:37 ` dpdklab
2025-04-22 12:38 ` dpdklab
2025-04-22 12:51 ` dpdklab
2025-04-22 12:56 ` dpdklab
2025-04-22 12:56 ` dpdklab
2025-04-22 12:57 ` dpdklab
2025-04-22 13:04 ` |PENDING| " dpdklab
2025-04-22 13:11 ` |WARNING| " dpdklab
2025-04-22 13:11 ` dpdklab
2025-04-22 13:17 ` |SUCCESS| " dpdklab
2025-04-22 13:34 ` dpdklab
2025-04-22 14:02 ` dpdklab
2025-04-22 15:48 ` 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=20250422113518.E83C5123FA7@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=changqing.li@windriver.com \
--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).