From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140880-140889 [PATCH v6 11/11] net/mlx5: initial design changes
Date: Sun, 9 Jun 2024 16:32:09 +0800 [thread overview]
Message-ID: <202406090832.4598W97R2898369@localhost.localdomain> (raw)
In-Reply-To: <20240609085600.87274-11-mkashani@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140889
_Compilation OK_
Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Sun, 9 Jun 2024 11:55:50 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 2bf363ff7e924a1fb6054eee693fde66097273f7
140880-140889 --> 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 9:00 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240609085600.87274-11-mkashani@nvidia.com>
2024-06-09 8:32 ` qemudev [this message]
2024-06-09 8:36 ` qemudev
2024-06-09 8:58 ` |SUCCESS| pw140889 " checkpatch
2024-06-09 10:01 ` |FAILURE| pw140880-140889 [PATCH] [v6,11/11] net/mlx5: initial desig dpdklab
2024-06-09 10:02 ` dpdklab
2024-06-09 10:02 ` |WARNING| " dpdklab
2024-06-09 10:02 ` dpdklab
2024-06-09 10:03 ` dpdklab
2024-06-09 10:03 ` dpdklab
2024-06-09 10:03 ` dpdklab
2024-06-09 10:03 ` |FAILURE| " dpdklab
2024-06-09 10:03 ` dpdklab
2024-06-09 10:03 ` dpdklab
2024-06-09 10:04 ` dpdklab
2024-06-09 10:04 ` dpdklab
2024-06-09 10:04 ` |WARNING| " dpdklab
2024-06-09 10:04 ` |FAILURE| " dpdklab
2024-06-09 10:04 ` |WARNING| " dpdklab
2024-06-09 10:04 ` |FAILURE| " dpdklab
2024-06-09 10:05 ` dpdklab
2024-06-09 10:05 ` dpdklab
2024-06-09 10:05 ` dpdklab
2024-06-09 10:05 ` |WARNING| " dpdklab
2024-06-09 10:05 ` |FAILURE| " dpdklab
2024-06-09 10:05 ` dpdklab
2024-06-09 10:05 ` dpdklab
2024-06-09 10:05 ` dpdklab
2024-06-09 10:05 ` dpdklab
2024-06-09 10:06 ` dpdklab
2024-06-09 10:06 ` dpdklab
2024-06-09 10:06 ` |WARNING| " dpdklab
2024-06-09 10:06 ` |FAILURE| " dpdklab
2024-06-09 10:06 ` dpdklab
2024-06-09 10:06 ` dpdklab
2024-06-09 10:06 ` dpdklab
2024-06-09 10:07 ` dpdklab
2024-06-09 10:07 ` dpdklab
2024-06-09 10:07 ` dpdklab
2024-06-09 10:07 ` dpdklab
2024-06-09 10:07 ` dpdklab
2024-06-09 10:07 ` dpdklab
2024-06-09 10:08 ` dpdklab
2024-06-09 10:08 ` dpdklab
2024-06-09 10:08 ` dpdklab
2024-06-09 10:08 ` dpdklab
2024-06-09 10:08 ` dpdklab
2024-06-09 10:09 ` dpdklab
2024-06-09 10:09 ` dpdklab
2024-06-09 10:09 ` dpdklab
2024-06-09 10:09 ` dpdklab
2024-06-09 10:09 ` dpdklab
2024-06-09 10:09 ` dpdklab
2024-06-09 10:11 ` dpdklab
2024-06-09 10:11 ` dpdklab
2024-06-09 10:11 ` dpdklab
2024-06-09 10:11 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:12 ` dpdklab
2024-06-09 10:13 ` dpdklab
2024-06-09 10:13 ` dpdklab
2024-06-09 10:13 ` dpdklab
2024-06-09 10:14 ` dpdklab
2024-06-09 10:14 ` dpdklab
2024-06-09 10:14 ` dpdklab
2024-06-09 10:14 ` dpdklab
2024-06-09 10:14 ` |WARNING| " dpdklab
2024-06-09 10:15 ` |FAILURE| " dpdklab
2024-06-09 10:15 ` dpdklab
2024-06-09 10:16 ` dpdklab
2024-06-09 10:33 ` dpdklab
2024-06-09 10:34 ` dpdklab
2024-06-09 10:37 ` 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=202406090832.4598W97R2898369@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).