From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw154615-154614 [PATCH 2/2] net/mlx5: support IPIP flow for all combinations
Date: Fri, 20 Jun 2025 18:09:17 +0800 [thread overview]
Message-ID: <202506201009.55KA9H1J423077@localhost.localdomain> (raw)
In-Reply-To: <20250620104203.261435-3-junfengg@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/154614
_Compilation OK_
Submitter: Junfeng Guo <junfengg@nvidia.com>
Date: Fri, 20 Jun 2025 13:42:02 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 77ba8d12251b203a4ec69a569c2f2f07edb7b1e8
154615-154614 --> 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:[~2025-06-20 10:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250620104203.261435-3-junfengg@nvidia.com>
2025-06-20 10:09 ` qemudev [this message]
2025-06-20 10:13 ` qemudev
2025-06-20 10:42 ` |SUCCESS| pw154614 " checkpatch
2025-06-20 11:21 ` |PENDING| pw154615-154614 [PATCH] [2/2] net/mlx5: support IPIP flow dpdklab
2025-06-20 11:31 ` |SUCCESS| " dpdklab
2025-06-20 11:32 ` dpdklab
2025-06-20 11:37 ` |FAILURE| " dpdklab
2025-06-20 11:38 ` dpdklab
2025-06-20 11:39 ` |SUCCESS| " dpdklab
2025-06-20 11:41 ` |PENDING| " dpdklab
2025-06-20 11:45 ` |SUCCESS| " dpdklab
2025-06-20 11:51 ` |SUCCESS| pw154614 [PATCH 2/2] net/mlx5: support IPIP flow for all combinations 0-day Robot
2025-06-20 11:54 ` |SUCCESS| pw154615-154614 [PATCH] [2/2] net/mlx5: support IPIP flow dpdklab
2025-06-20 12:01 ` |FAILURE| " dpdklab
2025-06-20 12:02 ` dpdklab
2025-06-20 12:07 ` |SUCCESS| " dpdklab
2025-06-20 12:20 ` dpdklab
2025-06-20 12:49 ` |FAILURE| " dpdklab
2025-06-20 13:42 ` |SUCCESS| " 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=202506201009.55KA9H1J423077@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).