From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chengwen Feng <fengchengwen@huawei.com>
Subject: |WARNING| pw139606 [PATCH v8] ethdev: fix strict aliasing lead to link cannot be up
Date: Mon, 22 Apr 2024 08:41:34 +0200 (CEST) [thread overview]
Message-ID: <20240422064134.53C3B124858@dpdk.org> (raw)
In-Reply-To: <20240422063813.23814-1-fengchengwen@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/139606
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#65:
[1] https://inbox.dpdk.org/dev/8175c905-e661-b910-7f20-59b6ab605c38@huawei.com/
total: 0 errors, 1 warnings, 94 lines checked
next prev parent reply other threads:[~2024-04-22 6:41 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240422063813.23814-1-fengchengwen@huawei.com>
2024-04-22 6:26 ` |SUCCESS| " qemudev
2024-04-22 6:31 ` qemudev
2024-04-22 6:41 ` checkpatch [this message]
2024-04-22 7:26 ` |SUCCESS| pw139606 [PATCH] [v8] ethdev: fix strict aliasing lead to dpdklab
2024-04-22 7:27 ` dpdklab
2024-04-22 7:37 ` dpdklab
2024-04-22 7:37 ` dpdklab
2024-04-22 7:38 ` dpdklab
2024-04-22 7:39 ` dpdklab
2024-04-22 7:40 ` dpdklab
2024-04-22 7:40 ` dpdklab
2024-04-22 7:41 ` dpdklab
2024-04-22 7:42 ` dpdklab
2024-04-22 7:44 ` dpdklab
2024-04-22 7:44 ` |SUCCESS| pw139606 [PATCH v8] ethdev: fix strict aliasing lead to link cannot be up 0-day Robot
2024-04-22 7:45 ` |SUCCESS| pw139606 [PATCH] [v8] ethdev: fix strict aliasing lead to dpdklab
2024-04-22 7:46 ` dpdklab
2024-04-22 7:46 ` dpdklab
2024-04-22 7:47 ` dpdklab
2024-04-22 7:49 ` dpdklab
2024-04-22 7:50 ` dpdklab
2024-04-22 7:50 ` dpdklab
2024-04-22 7:51 ` dpdklab
2024-04-22 7:51 ` dpdklab
2024-04-22 8:00 ` dpdklab
2024-04-22 8:01 ` dpdklab
2024-04-22 8:03 ` dpdklab
2024-04-22 8:03 ` dpdklab
2024-04-22 8:04 ` dpdklab
2024-04-22 8:05 ` dpdklab
2024-04-22 8:05 ` dpdklab
2024-04-22 8:06 ` dpdklab
2024-04-22 8:06 ` dpdklab
2024-04-22 8:07 ` dpdklab
2024-04-22 8:07 ` dpdklab
2024-04-22 8:08 ` dpdklab
2024-04-22 8:09 ` dpdklab
2024-04-22 8:10 ` dpdklab
2024-04-22 8:11 ` dpdklab
2024-04-22 8:12 ` dpdklab
2024-04-22 8:13 ` dpdklab
2024-04-22 8:13 ` dpdklab
2024-04-22 8:14 ` dpdklab
2024-04-22 8:15 ` dpdklab
2024-04-22 8:15 ` dpdklab
2024-04-22 8:16 ` dpdklab
2024-04-22 8:17 ` dpdklab
2024-04-22 8:17 ` dpdklab
2024-04-22 8:18 ` dpdklab
2024-04-22 8:19 ` dpdklab
2024-04-22 8:19 ` dpdklab
2024-04-22 8:20 ` dpdklab
2024-04-22 8:20 ` dpdklab
2024-04-22 8:21 ` dpdklab
2024-04-22 8:22 ` dpdklab
2024-04-22 8:23 ` dpdklab
2024-04-22 8:23 ` dpdklab
2024-04-22 8:23 ` dpdklab
2024-04-22 8:23 ` dpdklab
2024-04-22 8:24 ` dpdklab
2024-04-22 8:24 ` dpdklab
2024-04-22 8:26 ` dpdklab
2024-04-22 8:27 ` dpdklab
2024-04-22 8:27 ` dpdklab
2024-04-22 8:28 ` dpdklab
2024-04-22 8:29 ` dpdklab
2024-04-22 8:29 ` dpdklab
2024-04-22 8:30 ` dpdklab
2024-04-22 8:30 ` dpdklab
2024-04-22 8:30 ` dpdklab
2024-04-22 8:30 ` dpdklab
2024-04-22 8:31 ` dpdklab
2024-04-22 8:31 ` dpdklab
2024-04-22 8:31 ` dpdklab
2024-04-22 8:32 ` dpdklab
2024-04-22 8:32 ` dpdklab
2024-04-22 8:32 ` dpdklab
2024-04-22 8:32 ` dpdklab
2024-04-22 8:33 ` dpdklab
2024-04-22 8:33 ` dpdklab
2024-04-22 8:33 ` dpdklab
2024-04-22 8:57 ` dpdklab
2024-04-22 8:59 ` dpdklab
2024-04-22 8:59 ` dpdklab
2024-04-22 9:01 ` dpdklab
2024-04-22 9:02 ` dpdklab
2024-04-22 9:02 ` dpdklab
2024-04-22 9:07 ` dpdklab
2024-04-22 9:10 ` dpdklab
2024-04-22 9:13 ` dpdklab
2024-04-22 9:16 ` dpdklab
2024-04-22 9: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=20240422064134.53C3B124858@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=fengchengwen@huawei.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).