From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw139233 [PATCH v4] ethdev: fix strict aliasing lead to link cannot be up
Date: Fri, 12 Apr 2024 10:52:59 +0200 (CEST) [thread overview]
Message-ID: <20240412085259.35AEC121EEE@dpdk.org> (raw)
In-Reply-To: <20240412084949.4020-1-fengchengwen@huawei.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/139233
_coding style OK_
next prev parent reply other threads:[~2024-04-12 8:53 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240412084949.4020-1-fengchengwen@huawei.com>
2024-04-12 8:31 ` qemudev
2024-04-12 8:36 ` qemudev
2024-04-12 8:52 ` checkpatch [this message]
2024-04-12 9:44 ` 0-day Robot
2024-04-12 9:52 ` |SUCCESS| pw139233 [PATCH] [v4] ethdev: fix strict aliasing lead to dpdklab
2024-04-12 9:52 ` dpdklab
2024-04-12 9:53 ` dpdklab
2024-04-12 9:54 ` dpdklab
2024-04-12 9:54 ` dpdklab
2024-04-12 9:55 ` dpdklab
2024-04-12 9:55 ` dpdklab
2024-04-12 9:55 ` dpdklab
2024-04-12 9:55 ` dpdklab
2024-04-12 9:55 ` dpdklab
2024-04-12 9:56 ` dpdklab
2024-04-12 9:56 ` dpdklab
2024-04-12 9:57 ` dpdklab
2024-04-12 9:57 ` dpdklab
2024-04-12 9:57 ` dpdklab
2024-04-12 9:57 ` dpdklab
2024-04-12 9:57 ` dpdklab
2024-04-12 9:57 ` dpdklab
2024-04-12 9:58 ` dpdklab
2024-04-12 9:58 ` dpdklab
2024-04-12 9:58 ` dpdklab
2024-04-12 9:58 ` dpdklab
2024-04-12 9:59 ` dpdklab
2024-04-12 9:59 ` dpdklab
2024-04-12 9:59 ` dpdklab
2024-04-12 9:59 ` dpdklab
2024-04-12 9:59 ` dpdklab
2024-04-12 10:00 ` dpdklab
2024-04-12 10:00 ` dpdklab
2024-04-12 10:01 ` dpdklab
2024-04-12 10:01 ` dpdklab
2024-04-12 10:01 ` dpdklab
2024-04-12 10:01 ` dpdklab
2024-04-12 10:02 ` dpdklab
2024-04-12 10:02 ` dpdklab
2024-04-12 10:02 ` dpdklab
2024-04-12 10:02 ` dpdklab
2024-04-12 10:03 ` dpdklab
2024-04-12 10:03 ` dpdklab
2024-04-12 10:03 ` dpdklab
2024-04-12 10:03 ` dpdklab
2024-04-12 10:04 ` dpdklab
2024-04-12 10:04 ` dpdklab
2024-04-12 10:04 ` dpdklab
2024-04-12 10:04 ` dpdklab
2024-04-12 10:05 ` dpdklab
2024-04-12 10:05 ` dpdklab
2024-04-12 10:05 ` dpdklab
2024-04-12 10:05 ` dpdklab
2024-04-12 10:05 ` dpdklab
2024-04-12 10:06 ` dpdklab
2024-04-12 10:06 ` dpdklab
2024-04-12 10:07 ` dpdklab
2024-04-12 10:08 ` dpdklab
2024-04-12 10:09 ` dpdklab
2024-04-12 10:10 ` dpdklab
2024-04-12 10:10 ` dpdklab
2024-04-12 10:11 ` dpdklab
2024-04-12 10:13 ` dpdklab
2024-04-12 10:14 ` dpdklab
2024-04-12 10:14 ` dpdklab
2024-04-12 10:16 ` dpdklab
2024-04-12 10:17 ` dpdklab
2024-04-12 10:18 ` dpdklab
2024-04-12 10:18 ` dpdklab
2024-04-12 10:20 ` dpdklab
2024-04-12 10:22 ` dpdklab
2024-04-12 10:23 ` dpdklab
2024-04-12 10:23 ` dpdklab
2024-04-12 10:23 ` dpdklab
2024-04-12 10:25 ` dpdklab
2024-04-12 10:25 ` dpdklab
2024-04-12 10:25 ` dpdklab
2024-04-12 10:26 ` dpdklab
2024-04-12 10:28 ` dpdklab
2024-04-12 10:29 ` dpdklab
2024-04-12 10:30 ` dpdklab
2024-04-12 10:32 ` dpdklab
2024-04-12 10:35 ` dpdklab
2024-04-12 10:41 ` dpdklab
2024-04-12 11:00 ` dpdklab
2024-04-12 11:31 ` dpdklab
2024-04-12 11:40 ` dpdklab
2024-04-12 12:21 ` dpdklab
2024-04-12 12:42 ` dpdklab
2024-04-12 13:03 ` 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=20240412085259.35AEC121EEE@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).