From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <changqing.li@windriver.com>
Subject: |WARNING| pw153073 [PATCH V2] ethdev_trace.h: Update the trace point function when _TIME_BITS=64
Date: Tue, 22 Apr 2025 14:30:37 +0200 (CEST) [thread overview]
Message-ID: <20250422123037.CF1B8123FAA@dpdk.org> (raw)
In-Reply-To: <20250422122956.1217418-1-changqing.li@windriver.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153073
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#82:
498 | #define RTE_BUILD_BUG_ON(condition) ((void)sizeof(char[1 - 2*!!(condition)]))
total: 0 errors, 1 warnings, 99 lines checked
next prev parent reply other threads:[~2025-04-22 12:31 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250422122956.1217418-1-changqing.li@windriver.com>
2025-04-22 11:55 ` |SUCCESS| " qemudev
2025-04-22 12:00 ` qemudev
2025-04-22 12:30 ` checkpatch [this message]
2025-04-22 18:44 ` |SUCCESS| pw153073 [PATCH] [V2] ethdev_trace.h: Update the trace poi dpdklab
2025-04-22 19:07 ` dpdklab
2025-04-22 19:07 ` dpdklab
2025-04-22 19:15 ` dpdklab
2025-04-22 19:16 ` dpdklab
2025-04-22 19:17 ` dpdklab
2025-04-22 19:22 ` dpdklab
2025-04-22 19:28 ` dpdklab
2025-04-22 19:30 ` dpdklab
2025-04-22 19:32 ` dpdklab
2025-04-22 19:41 ` dpdklab
2025-04-22 19:42 ` dpdklab
2025-04-22 19:44 ` |PENDING| " dpdklab
2025-04-22 19:49 ` |SUCCESS| " dpdklab
2025-04-22 19:50 ` |WARNING| " dpdklab
2025-04-22 19:54 ` |SUCCESS| " dpdklab
2025-04-22 19:54 ` |PENDING| " dpdklab
2025-04-22 19:54 ` |SUCCESS| " dpdklab
2025-04-22 19:55 ` dpdklab
2025-04-22 20:00 ` dpdklab
2025-04-22 20:06 ` dpdklab
2025-04-22 20:10 ` dpdklab
2025-04-22 20:30 ` dpdklab
2025-04-22 20:31 ` |PENDING| " dpdklab
2025-04-22 20:34 ` |SUCCESS| " dpdklab
2025-04-22 20:37 ` dpdklab
2025-04-22 20:44 ` |WARNING| " dpdklab
2025-04-22 20:46 ` |PENDING| " dpdklab
2025-04-22 20:53 ` dpdklab
2025-04-22 20:58 ` |SUCCESS| " dpdklab
2025-04-22 21:00 ` dpdklab
2025-04-22 21:01 ` dpdklab
2025-04-22 21:10 ` |WARNING| " dpdklab
2025-04-22 21:18 ` |SUCCESS| " dpdklab
2025-04-22 21:46 ` dpdklab
2025-04-22 21:52 ` dpdklab
2025-04-22 21:52 ` dpdklab
2025-04-22 21:57 ` dpdklab
2025-04-22 22:06 ` dpdklab
2025-04-22 22:11 ` dpdklab
2025-04-22 22:52 ` dpdklab
2025-04-22 23:14 ` dpdklab
2025-04-22 23:19 ` 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=20250422123037.CF1B8123FAA@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).