From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw139278 [PATCH v6] ethdev: fix strict aliasing lead to link cannot be up
Date: Sat, 13 Apr 2024 10:52:09 +0200 (CEST) [thread overview]
Message-ID: <20240413085209.D892212083E@dpdk.org> (raw)
In-Reply-To: <20240413084840.33124-1-fengchengwen@huawei.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/139278
_coding style OK_
next prev parent reply other threads:[~2024-04-13 8:52 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240413084840.33124-1-fengchengwen@huawei.com>
2024-04-13 8:28 ` qemudev
2024-04-13 8:33 ` qemudev
2024-04-13 8:52 ` checkpatch [this message]
2024-04-13 9:43 ` 0-day Robot
2024-04-15 4:05 ` |SUCCESS| pw139278 [PATCH] [v6] ethdev: fix strict aliasing lead to dpdklab
2024-04-15 4:08 ` dpdklab
2024-04-15 4:08 ` dpdklab
2024-04-15 4:09 ` dpdklab
2024-04-15 4:09 ` dpdklab
2024-04-15 4:09 ` dpdklab
2024-04-15 4:10 ` dpdklab
2024-04-15 4:34 ` dpdklab
2024-04-15 4:38 ` dpdklab
2024-04-15 4:40 ` dpdklab
2024-04-15 4:41 ` dpdklab
2024-04-15 4:41 ` dpdklab
2024-04-15 4:42 ` dpdklab
2024-04-15 4:43 ` dpdklab
2024-04-15 4:43 ` dpdklab
2024-04-15 4:44 ` dpdklab
2024-04-15 4:44 ` dpdklab
2024-04-15 4:44 ` dpdklab
2024-04-15 4:44 ` dpdklab
2024-04-15 4:45 ` dpdklab
2024-04-15 4:45 ` dpdklab
2024-04-15 4:45 ` dpdklab
2024-04-15 4:45 ` dpdklab
2024-04-15 4:45 ` dpdklab
2024-04-15 4:46 ` dpdklab
2024-04-15 4:46 ` dpdklab
2024-04-15 4:46 ` dpdklab
2024-04-15 4:47 ` dpdklab
2024-04-15 4:47 ` dpdklab
2024-04-15 4:48 ` dpdklab
2024-04-15 4:48 ` dpdklab
2024-04-15 4:48 ` dpdklab
2024-04-15 4:49 ` dpdklab
2024-04-15 4:49 ` dpdklab
2024-04-15 4:49 ` dpdklab
2024-04-15 4:50 ` dpdklab
2024-04-15 4:50 ` dpdklab
2024-04-15 4:50 ` dpdklab
2024-04-15 4:51 ` dpdklab
2024-04-15 4:51 ` dpdklab
2024-04-15 4:51 ` dpdklab
2024-04-15 4:53 ` dpdklab
2024-04-15 4:53 ` dpdklab
2024-04-15 4:53 ` dpdklab
2024-04-15 4:53 ` dpdklab
2024-04-15 4:53 ` dpdklab
2024-04-15 4:54 ` dpdklab
2024-04-15 4:54 ` dpdklab
2024-04-15 4:54 ` dpdklab
2024-04-15 4:54 ` dpdklab
2024-04-15 4:55 ` dpdklab
2024-04-15 4:55 ` dpdklab
2024-04-15 4:55 ` dpdklab
2024-04-15 4:55 ` dpdklab
2024-04-15 4:55 ` dpdklab
2024-04-15 4:56 ` dpdklab
2024-04-15 4:56 ` dpdklab
2024-04-15 4:56 ` dpdklab
2024-04-15 4:58 ` dpdklab
2024-04-15 5:16 ` dpdklab
2024-04-15 5:18 ` dpdklab
2024-04-15 5:19 ` dpdklab
2024-04-15 5:37 ` dpdklab
2024-04-15 5:37 ` dpdklab
2024-04-15 5:45 ` dpdklab
2024-04-15 5:46 ` dpdklab
2024-04-15 5:46 ` dpdklab
2024-04-15 5:46 ` dpdklab
2024-04-15 5:47 ` dpdklab
2024-04-15 5:47 ` dpdklab
2024-04-15 5:49 ` dpdklab
2024-04-15 5:50 ` dpdklab
2024-04-15 5:51 ` dpdklab
2024-04-15 6:02 ` dpdklab
2024-04-15 6:03 ` dpdklab
2024-04-15 6:06 ` dpdklab
2024-04-15 6:07 ` dpdklab
2024-04-15 6:09 ` dpdklab
2024-04-15 6:09 ` dpdklab
2024-04-15 6:15 ` dpdklab
2024-04-15 6:17 ` dpdklab
2024-04-15 6:42 ` dpdklab
2024-04-15 6:49 ` dpdklab
2024-04-15 6:54 ` dpdklab
2024-04-15 7:37 ` 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=20240413085209.D892212083E@dpdk.org \
--to=checkpatch@dpdk.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).