From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140890-140900 [PATCH v7 11/11] net/mlx5: initial design changes
Date: Sun, 9 Jun 2024 18:35:50 +0800 [thread overview]
Message-ID: <202406091035.459AZoS9794595@localhost.localdomain> (raw)
In-Reply-To: <20240609110107.92009-11-mkashani@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140900
_Compilation OK_
Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Sun, 9 Jun 2024 14:00:57 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 2bf363ff7e924a1fb6054eee693fde66097273f7
140890-140900 --> 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-09 11:04 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240609110107.92009-11-mkashani@nvidia.com>
2024-06-09 10:35 ` qemudev [this message]
2024-06-09 10:40 ` qemudev
2024-06-09 11:05 ` |SUCCESS| pw140900 " checkpatch
2024-06-09 12:04 ` |WARNING| pw140890-140900 [PATCH] [v7,11/11] net/mlx5: initial desig dpdklab
2024-06-09 12:05 ` dpdklab
2024-06-09 12:05 ` |FAILURE| " dpdklab
2024-06-09 12:05 ` |WARNING| " dpdklab
2024-06-09 12:15 ` |FAILURE| " dpdklab
2024-06-09 12:15 ` |WARNING| " dpdklab
2024-06-09 12:15 ` |FAILURE| " dpdklab
2024-06-09 12:16 ` |WARNING| " dpdklab
2024-06-09 12:16 ` |FAILURE| " dpdklab
2024-06-09 12:16 ` |WARNING| " dpdklab
2024-06-09 12:16 ` |FAILURE| " dpdklab
2024-06-09 12:16 ` |WARNING| " dpdklab
2024-06-09 12:17 ` dpdklab
2024-06-09 12:17 ` |FAILURE| " dpdklab
2024-06-09 12:17 ` |WARNING| " dpdklab
2024-06-09 12:17 ` dpdklab
2024-06-09 12:18 ` |FAILURE| " dpdklab
2024-06-09 12:18 ` |WARNING| " dpdklab
2024-06-09 12:18 ` |FAILURE| " dpdklab
2024-06-09 12:19 ` |WARNING| " dpdklab
2024-06-09 12:19 ` |FAILURE| " dpdklab
2024-06-09 12:19 ` dpdklab
2024-06-09 12:19 ` |WARNING| " dpdklab
2024-06-09 12:19 ` dpdklab
2024-06-09 12:20 ` |FAILURE| " dpdklab
2024-06-09 12:20 ` dpdklab
2024-06-09 12:21 ` dpdklab
2024-06-09 12:21 ` dpdklab
2024-06-09 12:22 ` dpdklab
2024-06-09 12:22 ` dpdklab
2024-06-09 12:22 ` dpdklab
2024-06-09 12:23 ` dpdklab
2024-06-09 12:23 ` dpdklab
2024-06-09 12:23 ` dpdklab
2024-06-09 12:23 ` |SUCCESS| " dpdklab
2024-06-09 12:23 ` |FAILURE| " dpdklab
2024-06-09 12:24 ` dpdklab
2024-06-09 12:24 ` dpdklab
2024-06-09 12:24 ` dpdklab
2024-06-09 12:24 ` dpdklab
2024-06-09 12:24 ` dpdklab
2024-06-09 12:24 ` dpdklab
2024-06-09 12:25 ` dpdklab
2024-06-09 12:25 ` dpdklab
2024-06-09 12:25 ` dpdklab
2024-06-09 12:26 ` dpdklab
2024-06-09 12:26 ` dpdklab
2024-06-09 12:26 ` dpdklab
2024-06-09 12:26 ` dpdklab
2024-06-09 12:26 ` dpdklab
2024-06-09 12:27 ` dpdklab
2024-06-09 12:27 ` dpdklab
2024-06-09 12:27 ` dpdklab
2024-06-09 12:27 ` dpdklab
2024-06-09 12:27 ` dpdklab
2024-06-09 12:28 ` dpdklab
2024-06-09 12:28 ` dpdklab
2024-06-09 12:28 ` dpdklab
2024-06-09 12:28 ` dpdklab
2024-06-09 12:28 ` dpdklab
2024-06-09 12:28 ` dpdklab
2024-06-09 12:28 ` dpdklab
2024-06-09 12:28 ` dpdklab
2024-06-09 12:28 ` dpdklab
2024-06-09 12:29 ` dpdklab
2024-06-09 12:29 ` dpdklab
2024-06-09 12:29 ` dpdklab
2024-06-09 12:32 ` dpdklab
2024-06-09 12:33 ` dpdklab
2024-06-09 12:35 ` dpdklab
2024-06-09 12:35 ` dpdklab
2024-06-09 12:36 ` dpdklab
2024-06-09 12:38 ` dpdklab
2024-06-09 12:38 ` dpdklab
2024-06-09 12:39 ` dpdklab
2024-06-09 12:41 ` dpdklab
2024-06-09 12:42 ` dpdklab
2024-06-09 12:44 ` dpdklab
2024-06-09 12:46 ` dpdklab
2024-06-09 12:46 ` dpdklab
2024-06-09 12:47 ` dpdklab
2024-06-09 12: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=202406091035.459AZoS9794595@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).