From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139220 [PATCH] ethdev: fix strict aliasing lead to link cannot be up
Date: Thu, 11 Apr 2024 11:01:08 +0800 [thread overview]
Message-ID: <202404110301.43B31868554063@localhost.localdomain> (raw)
In-Reply-To: <20240411030749.41874-1-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139220
_Compilation OK_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Thu, 11 Apr 2024 03:07:49 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139220 --> 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-11 3:26 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240411030749.41874-1-fengchengwen@huawei.com>
2024-04-11 3:01 ` qemudev [this message]
2024-04-11 3:05 ` qemudev
2024-04-11 3:11 ` checkpatch
2024-04-11 3:44 ` |SUCCESS| pw139220 [PATCH] ethdev: fix strict aliasing lead to link dpdklab
2024-04-11 3:45 ` dpdklab
2024-04-11 3:45 ` dpdklab
2024-04-11 3:45 ` dpdklab
2024-04-11 3:46 ` dpdklab
2024-04-11 3:48 ` dpdklab
2024-04-11 3:48 ` dpdklab
2024-04-11 3:49 ` dpdklab
2024-04-11 3:49 ` dpdklab
2024-04-11 3:49 ` dpdklab
2024-04-11 3:50 ` dpdklab
2024-04-11 3:50 ` dpdklab
2024-04-11 3:50 ` dpdklab
2024-04-11 3:53 ` dpdklab
2024-04-11 3:54 ` dpdklab
2024-04-11 3:55 ` dpdklab
2024-04-11 3:56 ` dpdklab
2024-04-11 3:56 ` dpdklab
2024-04-11 3:56 ` dpdklab
2024-04-11 3:57 ` dpdklab
2024-04-11 3:58 ` dpdklab
2024-04-11 3:58 ` dpdklab
2024-04-11 3:59 ` dpdklab
2024-04-11 3:59 ` dpdklab
2024-04-11 4:00 ` dpdklab
2024-04-11 4:00 ` dpdklab
2024-04-11 4:00 ` dpdklab
2024-04-11 4:04 ` |FAILURE| pw139220 [PATCH] ethdev: fix strict aliasing lead to link cannot be up 0-day Robot
2024-04-11 4:23 ` |SUCCESS| pw139220 [PATCH] ethdev: fix strict aliasing lead to link dpdklab
2024-04-11 4:23 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:25 ` dpdklab
2024-04-11 4:25 ` dpdklab
2024-04-11 4:25 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:28 ` dpdklab
2024-04-11 4:28 ` dpdklab
2024-04-11 4:28 ` dpdklab
2024-04-11 4:28 ` dpdklab
2024-04-11 4:30 ` dpdklab
2024-04-11 4:30 ` dpdklab
2024-04-11 4:30 ` dpdklab
2024-04-11 4:31 ` dpdklab
2024-04-11 4:31 ` dpdklab
2024-04-11 4:31 ` dpdklab
2024-04-11 4:37 ` dpdklab
2024-04-11 4:38 ` dpdklab
2024-04-11 4:39 ` dpdklab
2024-04-11 4:39 ` dpdklab
2024-04-11 4:39 ` dpdklab
2024-04-11 4:40 ` dpdklab
2024-04-11 4:48 ` dpdklab
2024-04-11 5:03 ` dpdklab
2024-04-11 5:16 ` dpdklab
2024-04-11 5:16 ` dpdklab
2024-04-11 5:17 ` dpdklab
2024-04-11 5:17 ` dpdklab
2024-04-11 5:18 ` dpdklab
2024-04-11 5:19 ` dpdklab
2024-04-11 5:23 ` dpdklab
2024-04-11 5:24 ` dpdklab
2024-04-11 5:27 ` dpdklab
2024-04-11 5:29 ` dpdklab
2024-04-11 5:31 ` dpdklab
2024-04-11 5:34 ` dpdklab
2024-04-11 5:35 ` dpdklab
2024-04-11 5:36 ` dpdklab
2024-04-11 5:41 ` dpdklab
2024-04-11 5:48 ` dpdklab
2024-04-11 6:04 ` dpdklab
2024-04-11 6:08 ` dpdklab
2024-04-11 6:12 ` dpdklab
2024-04-11 6:13 ` 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=202404110301.43B31868554063@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).