From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw154831-154835 [PATCH v5 5/5] net/mlx5: use consecutive memory for Tx queue creation
Date: Mon, 30 Jun 2025 00:49:32 +0800 [thread overview]
Message-ID: <202506291649.55TGnWpd4012238@localhost.localdomain> (raw)
In-Reply-To: <20250629172303.72049-6-bingz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/154835
_Compilation OK_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Sun, 29 Jun 2025 20:22:59 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 5c0c1a13c34aa57c6e18f9ba852a9b5807c58b72
154831-154835 --> 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-29 17:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250629172303.72049-6-bingz@nvidia.com>
2025-06-29 16:49 ` qemudev [this message]
2025-06-29 16:54 ` qemudev
2025-06-29 17:23 ` |SUCCESS| pw154835 " checkpatch
2025-06-29 18:02 ` |FAILURE| " 0-day Robot
2025-06-29 19:41 ` |FAILURE| pw154831-154835 [PATCH] [v5,5/5] net/mlx5: use consecutive dpdklab
2025-06-29 19:57 ` dpdklab
2025-06-29 20:07 ` dpdklab
2025-06-29 20:15 ` |PENDING| " dpdklab
2025-06-29 20:24 ` |FAILURE| " dpdklab
2025-06-29 20:24 ` dpdklab
2025-06-29 20:27 ` dpdklab
2025-06-29 20:31 ` dpdklab
2025-06-29 20:33 ` dpdklab
2025-06-29 20:42 ` dpdklab
2025-06-29 20:42 ` dpdklab
2025-06-29 20:43 ` dpdklab
2025-06-29 20:45 ` |PENDING| " dpdklab
2025-06-29 21:01 ` |FAILURE| " dpdklab
2025-06-29 21:20 ` |WARNING| " dpdklab
2025-06-29 22:25 ` |FAILURE| " dpdklab
2025-06-29 22:54 ` |WARNING| " dpdklab
2025-06-29 22:54 ` dpdklab
2025-06-29 23:19 ` |FAILURE| " 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=202506291649.55TGnWpd4012238@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).