From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140725-140724 [PATCH v4 3/3] net/mlx5: implement VXLAN last reserved modification
Date: Tue, 4 Jun 2024 20:21:16 +0800 [thread overview]
Message-ID: <202406041221.454CLG1i3170832@localhost.localdomain> (raw)
In-Reply-To: <20240604123840.432044-4-rongweil@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140724
_Compilation OK_
Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Tue, 4 Jun 2024 15:38:37 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: a6bbf008457a455fcf4cf7374c280bba697a353f
140725-140724 --> 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-06-04 12:49 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240604123840.432044-4-rongweil@nvidia.com>
2024-06-04 12:21 ` qemudev [this message]
2024-06-04 12:25 ` qemudev
2024-06-04 12:40 ` |SUCCESS| pw140724 " checkpatch
2024-06-04 13:45 ` 0-day Robot
2024-06-04 16:24 ` |SUCCESS| pw140725-140724 [PATCH] [v4,3/3] net/mlx5: implement VXLAN dpdklab
2024-06-04 16:26 ` dpdklab
2024-06-04 16:37 ` dpdklab
2024-06-04 16:41 ` dpdklab
2024-06-04 17:13 ` dpdklab
2024-06-04 17:13 ` dpdklab
2024-06-04 17:17 ` dpdklab
2024-06-04 17:18 ` dpdklab
2024-06-04 17:19 ` dpdklab
2024-06-04 17:19 ` dpdklab
2024-06-04 17:19 ` dpdklab
2024-06-04 17:20 ` dpdklab
2024-06-04 17:20 ` dpdklab
2024-06-04 17:23 ` dpdklab
2024-06-04 17:23 ` dpdklab
2024-06-04 17:23 ` dpdklab
2024-06-04 17:24 ` dpdklab
2024-06-04 17:28 ` dpdklab
2024-06-04 17:31 ` dpdklab
2024-06-04 17:38 ` dpdklab
2024-06-04 17:38 ` dpdklab
2024-06-04 17:39 ` dpdklab
2024-06-04 17:41 ` dpdklab
2024-06-04 17:44 ` dpdklab
2024-06-04 17:45 ` dpdklab
2024-06-04 17:47 ` dpdklab
2024-06-04 17:50 ` dpdklab
2024-06-04 17:51 ` dpdklab
2024-06-04 17:52 ` dpdklab
2024-06-04 17:55 ` dpdklab
2024-06-04 17:56 ` dpdklab
2024-06-04 17:57 ` dpdklab
2024-06-04 18:00 ` dpdklab
2024-06-04 18:00 ` dpdklab
2024-06-04 18:01 ` dpdklab
2024-06-04 18:04 ` dpdklab
2024-06-04 18:15 ` dpdklab
2024-06-04 18:23 ` dpdklab
2024-06-04 18:24 ` dpdklab
2024-06-04 18:28 ` dpdklab
2024-06-04 18:29 ` dpdklab
2024-06-04 18:34 ` dpdklab
2024-06-04 18:34 ` dpdklab
2024-06-04 18:35 ` dpdklab
2024-06-04 18:37 ` dpdklab
2024-06-04 18:41 ` dpdklab
2024-06-04 18:44 ` dpdklab
2024-06-04 18:45 ` dpdklab
2024-06-04 18:48 ` dpdklab
2024-06-04 18:49 ` dpdklab
2024-06-04 18:49 ` dpdklab
2024-06-04 18:50 ` dpdklab
2024-06-04 18:53 ` dpdklab
2024-06-04 18:53 ` dpdklab
2024-06-04 19:03 ` dpdklab
2024-06-04 19:03 ` dpdklab
2024-06-04 19:04 ` dpdklab
2024-06-04 19:04 ` dpdklab
2024-06-04 19:04 ` dpdklab
2024-06-04 19:05 ` dpdklab
2024-06-04 19:05 ` dpdklab
2024-06-04 19:05 ` dpdklab
2024-06-04 19:06 ` dpdklab
2024-06-04 19:06 ` dpdklab
2024-06-04 19:06 ` dpdklab
2024-06-04 19:06 ` dpdklab
2024-06-04 19:07 ` dpdklab
2024-06-04 19:28 ` dpdklab
2024-06-04 19:29 ` dpdklab
2024-06-04 19:29 ` dpdklab
2024-06-04 19:29 ` dpdklab
2024-06-04 19:30 ` dpdklab
2024-06-04 19:30 ` dpdklab
2024-06-04 19:32 ` dpdklab
2024-06-04 19:32 ` dpdklab
2024-06-04 19:32 ` dpdklab
2024-06-04 19:32 ` dpdklab
2024-06-04 19:33 ` dpdklab
2024-06-04 19:33 ` dpdklab
2024-06-04 19:34 ` dpdklab
2024-06-04 19:34 ` dpdklab
2024-06-04 19:36 ` dpdklab
2024-06-04 19:36 ` dpdklab
2024-06-04 19:39 ` dpdklab
2024-06-04 19:39 ` dpdklab
2024-06-04 19:43 ` dpdklab
2024-06-04 19:56 ` dpdklab
2024-06-04 20:03 ` dpdklab
2024-06-04 20:05 ` dpdklab
2024-06-04 20:09 ` dpdklab
2024-06-04 20:09 ` dpdklab
2024-06-04 20:10 ` dpdklab
2024-06-04 20:36 ` dpdklab
2024-06-04 20:36 ` dpdklab
2024-06-04 21:50 ` dpdklab
2024-06-04 21:59 ` 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=202406041221.454CLG1i3170832@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).