From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw141122 [PATCH] net/mlx5: fix mlx5 device start failure
Date: Thu, 13 Jun 2024 20:23:23 +0800 [thread overview]
Message-ID: <202406131223.45DCNNr53971475@localhost.localdomain> (raw)
In-Reply-To: <20240613124528.547952-1-bingz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/141122
_Compilation OK_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Thu, 13 Jun 2024 15:45:28 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: c1cdfbcc339c2c951bff95854983a8773d9e5b8e
141122 --> 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-13 12:52 UTC|newest]
Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240613124528.547952-1-bingz@nvidia.com>
2024-06-13 12:23 ` qemudev [this message]
2024-06-13 12:27 ` qemudev
2024-06-13 12:46 ` checkpatch
2024-06-13 13:44 ` 0-day Robot
2024-06-13 15:56 ` dpdklab
2024-06-13 15:59 ` dpdklab
2024-06-13 16:00 ` dpdklab
2024-06-13 16:00 ` dpdklab
2024-06-13 16:01 ` dpdklab
2024-06-13 16:01 ` dpdklab
2024-06-13 16:03 ` dpdklab
2024-06-13 16:04 ` dpdklab
2024-06-13 16:05 ` dpdklab
2024-06-13 16:05 ` dpdklab
2024-06-13 16:07 ` dpdklab
2024-06-13 16:07 ` dpdklab
2024-06-13 16:07 ` dpdklab
2024-06-13 16:08 ` dpdklab
2024-06-13 16:44 ` dpdklab
2024-06-13 16:45 ` dpdklab
2024-06-13 16:46 ` dpdklab
2024-06-13 16:46 ` dpdklab
2024-06-13 16:46 ` dpdklab
2024-06-13 16:47 ` dpdklab
2024-06-13 16:48 ` dpdklab
2024-06-13 16:48 ` dpdklab
2024-06-13 16:48 ` dpdklab
2024-06-13 16:50 ` dpdklab
2024-06-13 16:50 ` dpdklab
2024-06-13 16:50 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:52 ` dpdklab
2024-06-13 16:52 ` dpdklab
2024-06-13 17:08 ` dpdklab
2024-06-13 17:27 ` dpdklab
2024-06-13 17:30 ` dpdklab
2024-06-13 17:33 ` dpdklab
2024-06-13 17:33 ` dpdklab
2024-06-13 17:34 ` dpdklab
2024-06-13 17:34 ` dpdklab
2024-06-13 17:35 ` dpdklab
2024-06-13 17:35 ` dpdklab
2024-06-13 17:36 ` dpdklab
2024-06-13 17:36 ` dpdklab
2024-06-13 17:36 ` dpdklab
2024-06-13 17:37 ` dpdklab
2024-06-13 17:37 ` dpdklab
2024-06-13 17:38 ` dpdklab
2024-06-13 17:39 ` dpdklab
2024-06-13 17:39 ` dpdklab
2024-06-13 17:40 ` dpdklab
2024-06-13 17:40 ` dpdklab
2024-06-13 17:40 ` dpdklab
2024-06-13 17:41 ` dpdklab
2024-06-13 17:41 ` dpdklab
2024-06-13 17:41 ` dpdklab
2024-06-13 17:42 ` dpdklab
2024-06-13 17:42 ` dpdklab
2024-06-13 17:42 ` dpdklab
2024-06-13 17:42 ` dpdklab
2024-06-13 17:43 ` dpdklab
2024-06-13 17:43 ` dpdklab
2024-06-13 17:43 ` dpdklab
2024-06-13 17:43 ` dpdklab
2024-06-13 17:43 ` dpdklab
2024-06-13 17:44 ` dpdklab
2024-06-13 17:44 ` dpdklab
2024-06-13 17:44 ` dpdklab
2024-06-13 17:44 ` dpdklab
2024-06-13 17:44 ` dpdklab
2024-06-13 17:44 ` dpdklab
2024-06-13 17:45 ` dpdklab
2024-06-13 17:45 ` dpdklab
2024-06-13 17:45 ` dpdklab
2024-06-13 17:45 ` dpdklab
2024-06-13 17:45 ` dpdklab
2024-06-13 17:45 ` dpdklab
2024-06-13 17:46 ` dpdklab
2024-06-13 17:46 ` dpdklab
2024-06-13 17:46 ` dpdklab
2024-06-13 17:46 ` dpdklab
2024-06-13 17:46 ` dpdklab
2024-06-13 17:46 ` dpdklab
2024-06-13 17:46 ` dpdklab
2024-06-13 17:47 ` dpdklab
2024-06-13 17:48 ` dpdklab
2024-06-13 17:48 ` dpdklab
2024-06-13 17:48 ` dpdklab
2024-06-13 17:49 ` dpdklab
2024-06-13 17:49 ` dpdklab
2024-06-13 17:51 ` dpdklab
2024-06-13 17:52 ` dpdklab
2024-06-13 17:54 ` dpdklab
2024-06-13 17:56 ` dpdklab
2024-06-13 17:58 ` dpdklab
2024-06-13 18:01 ` dpdklab
2024-06-13 18:01 ` dpdklab
2024-06-13 18:02 ` dpdklab
2024-06-13 18:04 ` dpdklab
2024-06-13 18:10 ` dpdklab
2024-06-13 18:11 ` dpdklab
2024-06-13 18:19 ` dpdklab
2024-06-13 20:11 ` dpdklab
2024-06-13 20:14 ` 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=202406131223.45DCNNr53971475@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).