From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124811 [PATCH v2] net/mlx5: enable hint in async table
Date: Mon, 6 Mar 2023 19:25:48 +0800 [thread overview]
Message-ID: <202303061125.326BPmMg4119582@localhost.localdomain> (raw)
In-Reply-To: <20230306113652.2311599-1-rongweil@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124811
_Compilation OK_
Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Mon, 6 Mar 2023 13:36:52 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 889996da9454bbdd260c40b4e085498884a760da
124811 --> 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:[~2023-03-06 11:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230306113652.2311599-1-rongweil@nvidia.com>
2023-03-06 11:25 ` qemudev [this message]
2023-03-06 11:29 ` qemudev
2023-03-06 11:38 ` checkpatch
2023-03-06 13:39 ` 0-day Robot
2023-03-06 12:05 |SUCCESS| pw124811 [PATCH] [v2] " dpdklab
2023-03-06 12:07 dpdklab
2023-03-06 12:11 dpdklab
2023-03-06 12:12 dpdklab
2023-03-06 12:18 dpdklab
2023-03-06 12:18 dpdklab
2023-03-06 12:19 dpdklab
2023-03-06 12:21 dpdklab
2023-03-06 12:23 dpdklab
2023-03-06 12:32 dpdklab
2023-03-06 12:34 dpdklab
2023-03-06 12:47 dpdklab
2023-03-06 12:48 dpdklab
2023-03-06 12:48 dpdklab
2023-03-06 12:48 dpdklab
2023-03-06 12:50 dpdklab
2023-03-06 12:58 dpdklab
2023-03-06 13:01 dpdklab
2023-03-06 13:01 dpdklab
2023-03-06 13:08 dpdklab
2023-03-06 13:09 dpdklab
2023-03-06 13:11 dpdklab
2023-03-06 13:13 dpdklab
2023-03-06 13:13 dpdklab
2023-03-06 13:20 dpdklab
2023-03-06 13:22 dpdklab
2023-03-06 13:22 dpdklab
2023-03-06 14:23 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=202303061125.326BPmMg4119582@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).