From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140384 [PATCH] net/mlx5: support HW flag action
Date: Tue, 28 May 2024 17:23:44 +0800 [thread overview]
Message-ID: <202405280923.44S9Nic53918256@localhost.localdomain> (raw)
In-Reply-To: <20240528095026.591845-1-shunh@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140384
_Compilation OK_
Submitter: Shun Hao <shunh@nvidia.com>
Date: Tue, 28 May 2024 12:50:26 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 5d185b9afaca3c98d8fd779e97d83e571660f4cf
140384 --> 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-28 9:52 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240528095026.591845-1-shunh@nvidia.com>
2024-05-28 9:23 ` qemudev [this message]
2024-05-28 9:27 ` qemudev
2024-05-28 9:51 ` checkpatch
2024-05-28 10:43 ` 0-day Robot
2024-05-28 11:53 ` dpdklab
2024-05-28 11:56 ` dpdklab
2024-05-28 11:56 ` dpdklab
2024-05-28 11:58 ` dpdklab
2024-05-28 11:58 ` dpdklab
2024-05-28 12:15 ` dpdklab
2024-05-28 12:59 ` dpdklab
2024-05-28 13:00 ` dpdklab
2024-05-28 13:08 ` dpdklab
2024-05-28 13:10 ` dpdklab
2024-05-28 13:15 ` dpdklab
2024-05-28 13:16 ` dpdklab
2024-05-28 13:18 ` dpdklab
2024-05-28 13:18 ` dpdklab
2024-05-28 13:19 ` dpdklab
2024-05-28 13:19 ` dpdklab
2024-05-28 13:19 ` dpdklab
2024-05-28 13:19 ` dpdklab
2024-05-28 13:20 ` dpdklab
2024-05-28 13:21 ` dpdklab
2024-05-28 13:27 ` dpdklab
2024-05-28 13:27 ` dpdklab
2024-05-28 14:10 ` dpdklab
2024-05-28 14:13 ` dpdklab
2024-05-28 14:14 ` dpdklab
2024-05-28 14:16 ` dpdklab
2024-05-28 14:16 ` dpdklab
2024-05-28 14:17 ` dpdklab
2024-05-28 14:18 ` dpdklab
2024-05-28 14:20 ` dpdklab
2024-05-28 14:21 ` dpdklab
2024-05-28 14:22 ` dpdklab
2024-05-28 14:22 ` dpdklab
2024-05-28 14:24 ` dpdklab
2024-05-28 14:25 ` dpdklab
2024-05-28 14:25 ` dpdklab
2024-05-28 14:26 ` dpdklab
2024-05-28 14:27 ` dpdklab
2024-05-28 14:27 ` dpdklab
2024-05-28 14:27 ` dpdklab
2024-05-28 14:28 ` dpdklab
2024-05-28 14:28 ` dpdklab
2024-05-28 14:28 ` dpdklab
2024-05-28 14:29 ` dpdklab
2024-05-28 14:30 ` dpdklab
2024-05-28 14:30 ` dpdklab
2024-05-28 14:31 ` dpdklab
2024-05-28 14:31 ` dpdklab
2024-05-28 14:32 ` dpdklab
2024-05-28 14:32 ` dpdklab
2024-05-28 14:33 ` dpdklab
2024-05-28 14:33 ` dpdklab
2024-05-28 14:34 ` dpdklab
2024-05-28 14:34 ` dpdklab
2024-05-28 14:34 ` dpdklab
2024-05-28 14:35 ` dpdklab
2024-05-28 14:35 ` dpdklab
2024-05-28 14:35 ` dpdklab
2024-05-28 14:36 ` dpdklab
2024-05-28 14:36 ` dpdklab
2024-05-28 14:36 ` dpdklab
2024-05-28 14:37 ` dpdklab
2024-05-28 14:38 ` dpdklab
2024-05-28 14:38 ` dpdklab
2024-05-28 14:39 ` dpdklab
2024-05-28 14:40 ` dpdklab
2024-05-28 14:40 ` dpdklab
2024-05-28 14:40 ` dpdklab
2024-05-28 14:41 ` dpdklab
2024-05-28 14:42 ` dpdklab
2024-05-28 14:42 ` dpdklab
2024-05-28 14:42 ` dpdklab
2024-05-28 14:43 ` dpdklab
2024-05-28 14:44 ` dpdklab
2024-05-28 14:44 ` dpdklab
2024-05-28 14:45 ` dpdklab
2024-05-28 15:06 ` dpdklab
2024-05-28 15:08 ` dpdklab
2024-05-28 15:16 ` dpdklab
2024-05-28 15:29 ` dpdklab
2024-05-28 15:36 ` dpdklab
2024-05-28 16:29 ` dpdklab
2024-05-28 16:30 ` dpdklab
2024-05-30 2:48 ` dpdklab
2024-05-30 2:48 ` dpdklab
2024-05-30 2:55 ` 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=202405280923.44S9Nic53918256@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).