From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143848-143849 [PATCH V1 3/3] net/mlx5/hws: print CQE error syndrome and more information
Date: Tue, 10 Sep 2024 15:33:05 +0800 [thread overview]
Message-ID: <202409100733.48A7X5N83493384@localhost.localdomain> (raw)
In-Reply-To: <20240910075853.292823-4-gavinl@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143849
_Compilation OK_
Submitter: Gavin Li <gavinl@nvidia.com>
Date: Tue, 10 Sep 2024 10:58:51 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 1afebcc334d9a19f94b87062815067f77a195f76
143848-143849 --> 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-09-10 8:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240910075853.292823-4-gavinl@nvidia.com>
2024-09-10 7:33 ` qemudev [this message]
2024-09-10 7:37 ` qemudev
2024-09-10 8:00 ` |WARNING| pw143849 " checkpatch
2024-09-10 9:04 ` |SUCCESS| " 0-day Robot
2024-09-10 23:49 ` |SUCCESS| pw143848-143849 [PATCH] [V1,3/3] net/mlx5/hws: print CQE e dpdklab
2024-09-11 0:18 ` dpdklab
2024-09-11 1:17 ` dpdklab
2024-09-11 2:19 ` |PENDING| " dpdklab
2024-09-11 2:52 ` |SUCCESS| " dpdklab
2024-09-11 3:02 ` |PENDING| " dpdklab
2024-09-11 3:17 ` dpdklab
2024-09-11 4:58 ` |SUCCESS| " dpdklab
2024-09-11 5:12 ` dpdklab
2024-09-11 5:14 ` dpdklab
2024-09-11 5:14 ` dpdklab
2024-09-11 7:21 ` dpdklab
2024-09-11 9:13 ` dpdklab
2024-09-11 9:14 ` dpdklab
2024-09-11 10:25 ` dpdklab
2024-09-11 10:30 ` dpdklab
2024-09-11 10:49 ` dpdklab
2024-09-11 10:54 ` dpdklab
2024-09-11 10:59 ` dpdklab
2024-09-11 11:16 ` dpdklab
2024-09-11 16:12 ` dpdklab
2024-09-15 22:08 ` dpdklab
2024-09-16 3:50 ` 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=202409100733.48A7X5N83493384@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).