From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw155055 [PATCH] net/mlx5: fix out of order completions in ordinary Rx burst
Date: Tue, 8 Jul 2025 17:19:24 +0800 [thread overview]
Message-ID: <202507080919.5689JOeK3627007@localhost.localdomain> (raw)
In-Reply-To: <20250708095341.441890-1-viacheslavo@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/155055
_Compilation OK_
Submitter: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date: Tue, 8 Jul 2025 12:53:41 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: e2888614268cbf0abcc7cd72ad97ff4e4901d0a5
155055 --> 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-08 9:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250708095341.441890-1-viacheslavo@nvidia.com>
2025-07-08 9:19 ` qemudev [this message]
2025-07-08 9:23 ` qemudev
2025-07-08 9:53 ` checkpatch
2025-07-08 10:43 ` 0-day Robot
2025-07-08 10:57 ` |SUCCESS| pw155055 [PATCH] net/mlx5: fix out of order completions in dpdklab
2025-07-08 11:04 ` dpdklab
2025-07-08 11:07 ` |PENDING| " dpdklab
2025-07-08 11:07 ` |SUCCESS| " dpdklab
2025-07-08 11:09 ` |PENDING| " dpdklab
2025-07-08 11:11 ` |SUCCESS| " dpdklab
2025-07-08 11:12 ` dpdklab
2025-07-08 11:29 ` |PENDING| " dpdklab
2025-07-08 11:37 ` |SUCCESS| " dpdklab
2025-07-08 12:03 ` |FAILURE| " dpdklab
2025-07-08 12:14 ` |SUCCESS| " dpdklab
2025-07-08 12:15 ` dpdklab
2025-07-08 12:21 ` dpdklab
2025-07-08 12:47 ` dpdklab
2025-07-08 12:52 ` |WARNING| " dpdklab
2025-07-08 14:33 ` |SUCCESS| " dpdklab
2025-07-08 15:08 ` 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=202507080919.5689JOeK3627007@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).