From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140748-140747 [PATCH v2 3/3] net/mlx5: add external Tx queue map and unmap
Date: Wed, 5 Jun 2024 17:06:12 +0800 [thread overview]
Message-ID: <202406050906.45596Cxs3947131@localhost.localdomain> (raw)
In-Reply-To: <20240605093141.1826221-3-suanmingm@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140747
_Compilation OK_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Wed, 5 Jun 2024 17:31:39 +0800
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: a207de9a356ef890dd858064ee94e15f0841f0e1
140748-140747 --> 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-05 9:34 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240605093141.1826221-3-suanmingm@nvidia.com>
2024-06-05 9:06 ` qemudev [this message]
2024-06-05 9:10 ` qemudev
2024-06-05 9:32 ` |WARNING| pw140747 " checkpatch
2024-06-05 21:56 ` |SUCCESS| pw140748-140747 [PATCH] [v2,3/3] net/mlx5: add external Tx dpdklab
2024-06-05 21:57 ` dpdklab
2024-06-05 21:58 ` dpdklab
2024-06-05 21:58 ` dpdklab
2024-06-05 21:59 ` dpdklab
2024-06-05 21:59 ` dpdklab
2024-06-05 22:00 ` dpdklab
2024-06-05 22:00 ` dpdklab
2024-06-05 22:02 ` dpdklab
2024-06-05 22:03 ` dpdklab
2024-06-05 22:05 ` dpdklab
2024-06-05 22:05 ` dpdklab
2024-06-05 22:16 ` dpdklab
2024-06-05 22:17 ` dpdklab
2024-06-05 22:20 ` dpdklab
2024-06-05 22:20 ` dpdklab
2024-06-05 22:20 ` dpdklab
2024-06-05 22:20 ` dpdklab
2024-06-05 22:21 ` dpdklab
2024-06-05 22:21 ` dpdklab
2024-06-05 22:21 ` dpdklab
2024-06-05 22:22 ` dpdklab
2024-06-05 22:23 ` dpdklab
2024-06-05 22:27 ` dpdklab
2024-06-05 22:30 ` dpdklab
2024-06-05 22:30 ` dpdklab
2024-06-05 22:32 ` dpdklab
2024-06-05 22:34 ` dpdklab
2024-06-05 22:38 ` dpdklab
2024-06-05 22:43 ` dpdklab
2024-06-05 22:45 ` dpdklab
2024-06-05 22:54 ` dpdklab
2024-06-05 22:55 ` dpdklab
2024-06-05 23:07 ` dpdklab
2024-06-05 23:08 ` dpdklab
2024-06-05 23:08 ` dpdklab
2024-06-05 23:09 ` dpdklab
2024-06-05 23:16 ` dpdklab
2024-06-05 23:17 ` dpdklab
2024-06-05 23:20 ` dpdklab
2024-06-05 23:20 ` dpdklab
2024-06-05 23:21 ` dpdklab
2024-06-05 23:21 ` dpdklab
2024-06-05 23:25 ` dpdklab
2024-06-05 23:26 ` dpdklab
2024-06-05 23:26 ` dpdklab
2024-06-05 23:27 ` dpdklab
2024-06-05 23:28 ` dpdklab
2024-06-05 23:29 ` dpdklab
2024-06-05 23:31 ` dpdklab
2024-06-05 23:33 ` dpdklab
2024-06-05 23:36 ` dpdklab
2024-06-05 23:36 ` dpdklab
2024-06-05 23:37 ` dpdklab
2024-06-05 23:38 ` dpdklab
2024-06-05 23:42 ` dpdklab
2024-06-05 23:43 ` dpdklab
2024-06-05 23:44 ` dpdklab
2024-06-05 23:44 ` dpdklab
2024-06-05 23:46 ` dpdklab
2024-06-05 23:47 ` dpdklab
2024-06-05 23:48 ` dpdklab
2024-06-05 23:52 ` dpdklab
2024-06-05 23:53 ` dpdklab
2024-06-05 23:54 ` dpdklab
2024-06-05 23:55 ` dpdklab
2024-06-05 23:55 ` dpdklab
2024-06-05 23:55 ` dpdklab
2024-06-05 23:56 ` dpdklab
2024-06-05 23:57 ` dpdklab
2024-06-05 23:57 ` dpdklab
2024-06-05 23:58 ` dpdklab
2024-06-06 0:00 ` dpdklab
2024-06-06 0:01 ` dpdklab
2024-06-06 0:01 ` dpdklab
2024-06-06 0:04 ` dpdklab
2024-06-06 0:05 ` dpdklab
2024-06-06 0:07 ` dpdklab
2024-06-06 0:07 ` dpdklab
2024-06-06 0:16 ` dpdklab
2024-06-06 0:16 ` dpdklab
2024-06-06 0:16 ` dpdklab
2024-06-06 0:16 ` dpdklab
2024-06-06 0:16 ` dpdklab
2024-06-06 0:18 ` dpdklab
2024-06-06 0:45 ` dpdklab
2024-06-06 0:47 ` dpdklab
2024-06-06 1:21 ` dpdklab
2024-06-06 1:22 ` dpdklab
2024-06-06 2:59 ` dpdklab
2024-06-06 6:03 ` dpdklab
2024-06-06 6:10 ` dpdklab
2024-06-06 6:35 ` 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=202406050906.45596Cxs3947131@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).