From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140290 [PATCH] doc: add firmware update links in mlx5 guide
Date: Thu, 23 May 2024 19:02:48 +0800 [thread overview]
Message-ID: <202405231102.44NB2mqO1694383@localhost.localdomain> (raw)
In-Reply-To: <20240523112850.1446671-1-thomas@monjalon.net>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140290
_Compilation OK_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Thu, 23 May 2024 13:28:49 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 58242360b798ccd45190fc9bc68292f26b7c4385
140290 --> 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-05-23 11:31 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240523112850.1446671-1-thomas@monjalon.net>
2024-05-23 11:02 ` qemudev [this message]
2024-05-23 11:07 ` qemudev
2024-05-23 11:30 ` checkpatch
2024-05-23 12:21 ` |SUCCESS| pw140290 [PATCH] doc: add firmware update links in mlx5 gu dpdklab
2024-05-23 12:22 ` dpdklab
2024-05-23 12:24 ` |SUCCESS| pw140290 [PATCH] doc: add firmware update links in mlx5 guide 0-day Robot
2024-05-23 12:25 ` |SUCCESS| pw140290 [PATCH] doc: add firmware update links in mlx5 gu dpdklab
2024-05-23 12:26 ` dpdklab
2024-05-23 12:26 ` dpdklab
2024-05-23 12:26 ` dpdklab
2024-05-23 12:28 ` dpdklab
2024-05-23 12:29 ` dpdklab
2024-05-23 12:29 ` dpdklab
2024-05-23 12:32 ` dpdklab
2024-05-23 12:33 ` dpdklab
2024-05-23 12:34 ` dpdklab
2024-05-23 12:39 ` dpdklab
2024-05-23 12:42 ` dpdklab
2024-05-23 12:42 ` dpdklab
2024-05-23 12:42 ` dpdklab
2024-05-23 12:43 ` dpdklab
2024-05-23 12:43 ` dpdklab
2024-05-23 12:44 ` dpdklab
2024-05-23 12:44 ` dpdklab
2024-05-23 12:44 ` dpdklab
2024-05-23 12:45 ` dpdklab
2024-05-23 12:45 ` dpdklab
2024-05-23 12:48 ` dpdklab
2024-05-23 12:48 ` dpdklab
2024-05-23 12:48 ` dpdklab
2024-05-23 12:49 ` dpdklab
2024-05-23 12:49 ` dpdklab
2024-05-23 12:50 ` dpdklab
2024-05-23 12:50 ` dpdklab
2024-05-23 12:50 ` dpdklab
2024-05-23 12:51 ` dpdklab
2024-05-23 12:51 ` dpdklab
2024-05-23 12:51 ` dpdklab
2024-05-23 12:52 ` dpdklab
2024-05-23 12:52 ` dpdklab
2024-05-23 12:54 ` dpdklab
2024-05-23 12:54 ` dpdklab
2024-05-23 12:55 ` dpdklab
2024-05-23 12:55 ` dpdklab
2024-05-23 12:56 ` dpdklab
2024-05-23 12:56 ` dpdklab
2024-05-23 12:57 ` dpdklab
2024-05-23 12:57 ` dpdklab
2024-05-23 12:57 ` dpdklab
2024-05-23 12:57 ` dpdklab
2024-05-23 12:58 ` dpdklab
2024-05-23 12:58 ` dpdklab
2024-05-23 12:58 ` dpdklab
2024-05-23 12:59 ` dpdklab
2024-05-23 12:59 ` dpdklab
2024-05-23 12:59 ` dpdklab
2024-05-23 12:59 ` dpdklab
2024-05-23 12:59 ` dpdklab
2024-05-23 13:00 ` dpdklab
2024-05-23 13:00 ` dpdklab
2024-05-23 13:00 ` dpdklab
2024-05-23 13:00 ` dpdklab
2024-05-23 13:00 ` dpdklab
2024-05-23 13:01 ` dpdklab
2024-05-23 13:01 ` dpdklab
2024-05-23 13:01 ` dpdklab
2024-05-23 13:01 ` dpdklab
2024-05-23 13:01 ` dpdklab
2024-05-23 13:02 ` dpdklab
2024-05-23 13:02 ` dpdklab
2024-05-23 13:03 ` dpdklab
2024-05-23 13:04 ` dpdklab
2024-05-23 13:04 ` dpdklab
2024-05-23 13:05 ` dpdklab
2024-05-23 13:05 ` dpdklab
2024-05-23 13:05 ` dpdklab
2024-05-23 13:06 ` dpdklab
2024-05-23 13:06 ` dpdklab
2024-05-23 13:09 ` dpdklab
2024-05-23 13:10 ` dpdklab
2024-05-23 13:12 ` dpdklab
2024-05-23 13:13 ` dpdklab
2024-05-23 13:16 ` dpdklab
2024-05-23 13:20 ` dpdklab
2024-05-23 13:21 ` dpdklab
2024-05-23 13:32 ` dpdklab
2024-05-23 13:53 ` dpdklab
2024-05-23 14:07 ` dpdklab
2024-05-23 14:08 ` dpdklab
2024-05-23 14:43 ` dpdklab
2024-05-23 15:44 ` 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=202405231102.44NB2mqO1694383@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).