From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137673 [PATCH] crypto/mlx5: add virtual function device ID
Date: Sat, 2 Mar 2024 14:10:19 +0800 [thread overview]
Message-ID: <202403020610.4226AJX13743645@localhost.localdomain> (raw)
In-Reply-To: <20240301123037.1216332-1-suanmingm@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137673
_Compilation OK_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Fri, 1 Mar 2024 20:30:37 +0800
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 5ac50824383c2683c0dfdf24c6dc493f1fa54852
137673 --> 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 prev parent reply other threads:[~2024-03-02 6:35 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240301123037.1216332-1-suanmingm@nvidia.com>
2024-03-01 12:32 ` checkpatch
2024-03-01 13:11 ` |SUCCESS| pw137673 [PATCH] crypto/mlx5: add virtual function device dpdklab
2024-03-01 13:12 ` |FAILURE| " dpdklab
2024-03-01 13:13 ` |SUCCESS| " dpdklab
2024-03-01 13:13 ` dpdklab
2024-03-01 13:13 ` dpdklab
2024-03-01 13:13 ` dpdklab
2024-03-01 13:14 ` dpdklab
2024-03-01 13:14 ` dpdklab
2024-03-01 13:15 ` dpdklab
2024-03-01 13:15 ` dpdklab
2024-03-01 13:15 ` dpdklab
2024-03-01 13:16 ` dpdklab
2024-03-01 13:16 ` dpdklab
2024-03-01 13:16 ` dpdklab
2024-03-01 13:16 ` dpdklab
2024-03-01 13:16 ` dpdklab
2024-03-01 13:16 ` dpdklab
2024-03-01 13:18 ` dpdklab
2024-03-01 13:24 ` dpdklab
2024-03-01 13:24 ` |SUCCESS| pw137673 [PATCH] crypto/mlx5: add virtual function device ID 0-day Robot
2024-03-01 13:25 ` |SUCCESS| pw137673 [PATCH] crypto/mlx5: add virtual function device dpdklab
2024-03-01 13:27 ` dpdklab
2024-03-01 13:28 ` |FAILURE| " dpdklab
2024-03-01 13:29 ` |SUCCESS| " dpdklab
2024-03-01 13:31 ` dpdklab
2024-03-01 13:31 ` dpdklab
2024-03-01 13:31 ` dpdklab
2024-03-01 13:31 ` dpdklab
2024-03-01 13:32 ` dpdklab
2024-03-01 13:32 ` dpdklab
2024-03-01 13:33 ` dpdklab
2024-03-01 13:33 ` |FAILURE| " dpdklab
2024-03-01 13:33 ` |SUCCESS| " dpdklab
2024-03-01 13:34 ` dpdklab
2024-03-01 13:34 ` dpdklab
2024-03-01 13:34 ` dpdklab
2024-03-01 13:34 ` dpdklab
2024-03-01 13:34 ` dpdklab
2024-03-01 13:34 ` dpdklab
2024-03-01 13:35 ` dpdklab
2024-03-01 13:35 ` dpdklab
2024-03-01 13:35 ` dpdklab
2024-03-01 13:36 ` dpdklab
2024-03-01 13:36 ` dpdklab
2024-03-01 13:36 ` dpdklab
2024-03-01 13:36 ` dpdklab
2024-03-01 13:37 ` dpdklab
2024-03-01 13:40 ` dpdklab
2024-03-01 13:40 ` dpdklab
2024-03-01 13:40 ` dpdklab
2024-03-01 13:41 ` dpdklab
2024-03-01 13:41 ` dpdklab
2024-03-01 13:41 ` dpdklab
2024-03-01 13:41 ` dpdklab
2024-03-01 13:41 ` dpdklab
2024-03-01 13:42 ` dpdklab
2024-03-01 13:46 ` dpdklab
2024-03-01 14:14 ` dpdklab
2024-03-01 14:16 ` dpdklab
2024-03-01 17:07 ` dpdklab
2024-03-01 17:56 ` dpdklab
2024-03-01 17:57 ` dpdklab
2024-03-01 18:05 ` |FAILURE| " dpdklab
2024-03-01 18:06 ` |SUCCESS| " dpdklab
2024-03-01 19:22 ` |FAILURE| " dpdklab
2024-03-01 19:44 ` |SUCCESS| " dpdklab
2024-03-02 3:00 ` dpdklab
2024-03-02 3:07 ` dpdklab
2024-03-02 6:10 ` qemudev [this message]
2024-03-02 6:14 ` |SUCCESS| pw137673 [PATCH] crypto/mlx5: add virtual function device ID qemudev
2024-03-02 17:24 ` |SUCCESS| pw137673 [PATCH] crypto/mlx5: add virtual function device dpdklab
2024-03-02 19:48 ` dpdklab
2024-03-02 19:55 ` dpdklab
2024-03-05 1:08 ` dpdklab
2024-03-05 1:41 ` dpdklab
2024-03-05 2:13 ` 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=202403020610.4226AJX13743645@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).