From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139606 [PATCH v8] ethdev: fix strict aliasing lead to link cannot be up
Date: Mon, 22 Apr 2024 14:26:40 +0800 [thread overview]
Message-ID: <202404220626.43M6QeoU430981@localhost.localdomain> (raw)
In-Reply-To: <20240422063813.23814-1-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139606
_Compilation OK_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Mon, 22 Apr 2024 06:38:13 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 7b668b7d65ba33783c280d08489fa31685bd0ee6
139606 --> meson & ninja build successfully
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
next parent reply other threads:[~2024-04-22 6:54 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 ` qemudev [this message]
2024-04-22 6:31 ` qemudev
2024-04-22 6:41 ` |WARNING| " checkpatch
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=202404220626.43M6QeoU430981@localhost.localdomain \
--to=qemudev@loongson.cn \
--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).