From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137435-137439 [PATCH v4 5/5] net/mlx5: validate the actions combination with NAT64
Date: Wed, 28 Feb 2024 22:48:54 +0800 [thread overview]
Message-ID: <202402281448.41SEmsAb1184641@localhost.localdomain> (raw)
In-Reply-To: <20240228150913.32603-6-bingz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137439
_Compilation OK_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Wed, 28 Feb 2024 17:09:09 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: f0cd4465b336362425eaae17fbaf7ac8f392da91
137435-137439 --> 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-02-28 15:14 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240228150913.32603-6-bingz@nvidia.com>
2024-02-28 14:48 ` qemudev [this message]
2024-02-28 14:53 ` qemudev
2024-02-28 15:13 ` |SUCCESS| pw137439 " checkpatch
2024-02-28 15:58 ` |SUCCESS| pw137435-137439 [PATCH] [v4,5/5] net/mlx5: validate the ac dpdklab
2024-02-28 15:58 ` dpdklab
2024-02-28 15:58 ` dpdklab
2024-02-28 15:59 ` dpdklab
2024-02-28 15:59 ` dpdklab
2024-02-28 15:59 ` dpdklab
2024-02-28 15:59 ` dpdklab
2024-02-28 16:06 ` dpdklab
2024-02-28 16:06 ` dpdklab
2024-02-28 16:06 ` dpdklab
2024-02-28 16:07 ` dpdklab
2024-02-28 16:07 ` dpdklab
2024-02-28 16:07 ` dpdklab
2024-02-28 16:07 ` dpdklab
2024-02-28 16:08 ` dpdklab
2024-02-28 16:08 ` dpdklab
2024-02-28 16:08 ` dpdklab
2024-02-28 16:08 ` dpdklab
2024-02-28 16:09 ` dpdklab
2024-02-28 16:09 ` dpdklab
2024-02-28 16:09 ` dpdklab
2024-02-28 16:09 ` dpdklab
2024-02-28 16:09 ` dpdklab
2024-02-28 16:09 ` dpdklab
2024-02-28 16:10 ` dpdklab
2024-02-28 16:10 ` dpdklab
2024-02-28 16:10 ` dpdklab
2024-02-28 16:10 ` dpdklab
2024-02-28 16:10 ` dpdklab
2024-02-28 16:12 ` dpdklab
2024-02-28 16:12 ` dpdklab
2024-02-28 16:12 ` dpdklab
2024-02-28 16:13 ` dpdklab
2024-02-28 16:13 ` dpdklab
2024-02-28 16:13 ` dpdklab
2024-02-28 16:13 ` dpdklab
2024-02-28 16:13 ` dpdklab
2024-02-28 16:14 ` dpdklab
2024-02-28 16:14 ` dpdklab
2024-02-28 16:14 ` dpdklab
2024-02-28 16:14 ` dpdklab
2024-02-28 16:14 ` dpdklab
2024-02-28 16:15 ` dpdklab
2024-02-28 16:15 ` dpdklab
2024-02-28 16:15 ` dpdklab
2024-02-28 16:15 ` dpdklab
2024-02-28 16:15 ` dpdklab
2024-02-28 16:16 ` dpdklab
2024-02-28 16:16 ` dpdklab
2024-02-28 16:16 ` dpdklab
2024-02-28 16:16 ` dpdklab
2024-02-28 16:17 ` dpdklab
2024-02-28 16:17 ` dpdklab
2024-02-28 16:18 ` dpdklab
2024-02-28 16:18 ` dpdklab
2024-02-28 16:18 ` dpdklab
2024-02-28 16:18 ` dpdklab
2024-02-28 16:39 ` dpdklab
2024-02-28 17:17 ` dpdklab
2024-02-28 18:43 ` dpdklab
2024-02-28 21:17 ` dpdklab
2024-02-28 21:24 ` dpdklab
2024-02-29 13:56 ` dpdklab
2024-02-29 23:37 ` dpdklab
2024-02-29 23:40 ` dpdklab
2024-02-29 23:41 ` dpdklab
2024-02-29 23:43 ` dpdklab
2024-03-01 23:37 ` dpdklab
2024-03-01 23:55 ` dpdklab
2024-03-02 0:10 ` 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=202402281448.41SEmsAb1184641@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).