From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138662 [PATCH v2] net/mlx5/hws: fix port ID for root table
Date: Thu, 21 Mar 2024 22:26:27 +0800 [thread overview]
Message-ID: <202403211426.42LEQR6N922377@localhost.localdomain> (raw)
In-Reply-To: <20240321144811.1574579-1-kliteyn@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138662
_Compilation OK_
Submitter: Yevgeny Kliteynik <kliteyn@nvidia.com>
Date: Thu, 21 Mar 2024 16:48:11 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138662 --> 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-03-21 14:51 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240321144811.1574579-1-kliteyn@nvidia.com>
2024-03-21 14:26 ` qemudev [this message]
2024-03-21 14:30 ` qemudev
2024-03-21 14:49 ` checkpatch
2024-03-21 16:05 ` 0-day Robot
2024-03-21 20:03 ` |SUCCESS| pw138662 [PATCH] [v2] net/mlx5/hws: fix port ID for root t dpdklab
2024-03-21 20:10 ` dpdklab
2024-03-21 20:10 ` dpdklab
2024-03-21 20:12 ` dpdklab
2024-03-21 20:12 ` dpdklab
2024-03-21 20:13 ` dpdklab
2024-03-21 20:13 ` dpdklab
2024-03-21 20:13 ` dpdklab
2024-03-21 20:13 ` dpdklab
2024-03-21 20:14 ` dpdklab
2024-03-21 20:15 ` dpdklab
2024-03-21 20:15 ` dpdklab
2024-03-21 20:16 ` dpdklab
2024-03-21 20:16 ` dpdklab
2024-03-21 20:35 ` dpdklab
2024-03-21 20:38 ` dpdklab
2024-03-21 20:38 ` dpdklab
2024-03-21 20:39 ` dpdklab
2024-03-21 20:40 ` dpdklab
2024-03-21 20:40 ` dpdklab
2024-03-21 20:40 ` dpdklab
2024-03-21 20:41 ` dpdklab
2024-03-21 20:41 ` dpdklab
2024-03-21 20:42 ` dpdklab
2024-03-21 20:43 ` dpdklab
2024-03-21 20:43 ` dpdklab
2024-03-21 20:49 ` dpdklab
2024-03-21 20:49 ` dpdklab
2024-03-21 20:50 ` dpdklab
2024-03-21 20:51 ` dpdklab
2024-03-21 20:51 ` dpdklab
2024-03-21 20:51 ` dpdklab
2024-03-21 20:53 ` dpdklab
2024-03-21 20:56 ` dpdklab
2024-03-21 20:58 ` dpdklab
2024-03-21 20:58 ` dpdklab
2024-03-21 20:59 ` dpdklab
2024-03-21 20:59 ` dpdklab
2024-03-21 21:00 ` dpdklab
2024-03-21 21:01 ` dpdklab
2024-03-21 21:01 ` dpdklab
2024-03-21 21:01 ` dpdklab
2024-03-21 21:03 ` dpdklab
2024-03-21 21:04 ` dpdklab
2024-03-21 21:06 ` dpdklab
2024-03-21 21:18 ` dpdklab
2024-03-21 21:19 ` dpdklab
2024-03-21 21:21 ` dpdklab
2024-03-21 21:22 ` dpdklab
2024-03-21 21:39 ` dpdklab
2024-03-21 21:40 ` dpdklab
2024-03-21 21:40 ` dpdklab
2024-03-21 21:41 ` dpdklab
2024-03-21 21:43 ` dpdklab
2024-03-21 21:43 ` dpdklab
2024-03-21 21:44 ` dpdklab
2024-03-21 21:44 ` dpdklab
2024-03-21 21:46 ` dpdklab
2024-03-21 21:49 ` dpdklab
2024-03-21 21:49 ` dpdklab
2024-03-21 21:50 ` dpdklab
2024-03-21 21:58 ` dpdklab
2024-03-21 21:58 ` dpdklab
2024-03-21 21:59 ` dpdklab
2024-03-21 21:59 ` dpdklab
2024-03-21 22:01 ` dpdklab
2024-03-21 22:04 ` dpdklab
2024-03-21 22:05 ` dpdklab
2024-03-21 22:10 ` dpdklab
2024-03-21 22:21 ` dpdklab
2024-03-21 22:22 ` dpdklab
2024-03-22 2:59 ` dpdklab
2024-03-23 12:23 ` dpdklab
2024-03-23 12:59 ` 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=202403211426.42LEQR6N922377@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).