From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw155605 [PATCH] net/mlx5: fix storage handling of shared Rx queues
Date: Thu, 31 Jul 2025 18:07:22 +0800 [thread overview]
Message-ID: <202507311007.56VA7Mlw536578@localhost.localdomain> (raw)
In-Reply-To: <20250731104138.61593-1-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/155605
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thu, 31 Jul 2025 13:41:38 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: b222395561638f89562e4ef42e1eabf2d6db43dd
155605 --> 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-07-31 10:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250731104138.61593-1-getelson@nvidia.com>
2025-07-31 10:07 ` qemudev [this message]
2025-07-31 10:11 ` qemudev
2025-07-31 10:42 ` checkpatch
2025-07-31 11:23 ` |SUCCESS| pw155605 [PATCH] net/mlx5: fix storage handling of shared dpdklab
2025-07-31 11:23 ` |PENDING| " dpdklab
2025-07-31 11:23 ` |SUCCESS| " dpdklab
2025-07-31 11:31 ` dpdklab
2025-07-31 11:36 ` dpdklab
2025-07-31 11:38 ` dpdklab
2025-07-31 11:39 ` dpdklab
2025-07-31 11:40 ` dpdklab
2025-07-31 11:40 ` dpdklab
2025-07-31 11:41 ` |PENDING| " dpdklab
2025-07-31 11:49 ` |SUCCESS| pw155605 [PATCH] net/mlx5: fix storage handling of shared Rx queues 0-day Robot
2025-07-31 11:56 ` |SUCCESS| pw155605 [PATCH] net/mlx5: fix storage handling of shared dpdklab
2025-07-31 12:01 ` dpdklab
2025-07-31 12:03 ` dpdklab
2025-07-31 12:21 ` dpdklab
2025-07-31 12:22 ` dpdklab
2025-07-31 14:58 ` 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=202507311007.56VA7Mlw536578@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).