From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140316-140319 [PATCH v2 4/4] net/mlx5: implement VXLAN last reserved modification
Date: Mon, 27 May 2024 10:22:27 +0800 [thread overview]
Message-ID: <202405270222.44R2MRUM2715976@localhost.localdomain> (raw)
In-Reply-To: <20240527024720.1099161-5-rongweil@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140319
_Compilation OK_
Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Mon, 27 May 2024 05:47:17 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 2dbb63594a9a985e2c8639b57f9fcd1468b9de97
140316-140319 --> 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-05-27 2:51 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240527024720.1099161-5-rongweil@nvidia.com>
2024-05-27 2:22 ` qemudev [this message]
2024-05-27 2:26 ` qemudev
2024-05-27 2:49 ` |SUCCESS| pw140319 " checkpatch
2024-05-27 3:20 ` |SUCCESS| pw140316-140319 [PATCH] [v2,4/4] net/mlx5: implement VXLAN dpdklab
2024-05-27 3:21 ` dpdklab
2024-05-27 3:21 ` dpdklab
2024-05-27 3:22 ` dpdklab
2024-05-27 3:22 ` dpdklab
2024-05-27 3:22 ` dpdklab
2024-05-27 3:23 ` dpdklab
2024-05-27 3:23 ` dpdklab
2024-05-27 3:24 ` dpdklab
2024-05-27 3:24 ` dpdklab
2024-05-27 3:26 ` dpdklab
2024-05-27 3:26 ` dpdklab
2024-05-27 3:27 ` dpdklab
2024-05-27 3:28 ` dpdklab
2024-05-27 3:28 ` dpdklab
2024-05-27 3:28 ` dpdklab
2024-05-27 3:29 ` dpdklab
2024-05-27 3:30 ` dpdklab
2024-05-27 3:31 ` dpdklab
2024-05-27 3:32 ` dpdklab
2024-05-27 3:33 ` dpdklab
2024-05-27 3:34 ` dpdklab
2024-05-27 3:35 ` dpdklab
2024-05-27 3:35 ` dpdklab
2024-05-27 3:36 ` dpdklab
2024-05-27 3:36 ` dpdklab
2024-05-27 3:36 ` dpdklab
2024-05-27 3:36 ` dpdklab
2024-05-27 3:38 ` dpdklab
2024-05-27 3:38 ` dpdklab
2024-05-27 3:39 ` dpdklab
2024-05-27 3:41 ` dpdklab
2024-05-27 3:42 ` dpdklab
2024-05-27 3:43 ` dpdklab
2024-05-27 3:43 ` |SUCCESS| pw140319 [PATCH v2 4/4] net/mlx5: implement VXLAN last reserved modification 0-day Robot
2024-05-27 3:45 ` |SUCCESS| pw140316-140319 [PATCH] [v2,4/4] net/mlx5: implement VXLAN dpdklab
2024-05-27 3:46 ` dpdklab
2024-05-27 3:46 ` dpdklab
2024-05-27 3:48 ` dpdklab
2024-05-27 3:48 ` dpdklab
2024-05-27 3:49 ` dpdklab
2024-05-27 3:50 ` dpdklab
2024-05-27 3:51 ` dpdklab
2024-05-27 3:51 ` dpdklab
2024-05-27 3:53 ` dpdklab
2024-05-27 3:56 ` dpdklab
2024-05-27 3:56 ` dpdklab
2024-05-27 3:56 ` dpdklab
2024-05-27 3:57 ` dpdklab
2024-05-27 3:59 ` dpdklab
2024-05-27 4:00 ` dpdklab
2024-05-27 4:00 ` dpdklab
2024-05-27 4:03 ` dpdklab
2024-05-27 4:13 ` dpdklab
2024-05-27 4:15 ` dpdklab
2024-05-27 4:16 ` dpdklab
2024-05-27 4:16 ` dpdklab
2024-05-27 4:16 ` dpdklab
2024-05-27 4:16 ` dpdklab
2024-05-27 4:16 ` dpdklab
2024-05-27 4:16 ` dpdklab
2024-05-27 4:17 ` dpdklab
2024-05-27 4:17 ` dpdklab
2024-05-27 4:17 ` dpdklab
2024-05-27 4:18 ` dpdklab
2024-05-27 4:18 ` dpdklab
2024-05-27 4:18 ` dpdklab
2024-05-27 4:18 ` dpdklab
2024-05-27 4:18 ` dpdklab
2024-05-27 4:19 ` dpdklab
2024-05-27 4:31 ` dpdklab
2024-05-27 4:37 ` dpdklab
2024-05-27 4:46 ` dpdklab
2024-05-27 4:48 ` dpdklab
2024-05-27 4:48 ` dpdklab
2024-05-27 4:49 ` dpdklab
2024-05-27 4:53 ` dpdklab
2024-05-27 4:53 ` dpdklab
2024-05-27 4:59 ` dpdklab
2024-05-27 5:00 ` dpdklab
2024-05-27 5:01 ` dpdklab
2024-05-27 5:02 ` dpdklab
2024-05-27 5:35 ` dpdklab
2024-05-27 5:44 ` dpdklab
2024-05-27 5:48 ` dpdklab
2024-05-29 6:22 ` dpdklab
2024-05-29 6:57 ` 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=202405270222.44R2MRUM2715976@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).