From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138482 [PATCH v2] app/test-crypto-perf: add throughput OOP decryption
Date: Tue, 19 Mar 2024 19:24:39 +0800 [thread overview]
Message-ID: <202403191124.42JBOdYF3271444@localhost.localdomain> (raw)
In-Reply-To: <20240319114623.1137757-1-suanmingm@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138482
_Compilation OK_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Tue, 19 Mar 2024 19:46:23 +0800
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 7f82e9c89f3514715533feb34f46ff1ea95c6f98
138482 --> 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-19 11:49 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240319114623.1137757-1-suanmingm@nvidia.com>
2024-03-19 11:24 ` qemudev [this message]
2024-03-19 11:29 ` qemudev
2024-03-19 11:47 ` checkpatch
2024-03-19 12:44 ` 0-day Robot
2024-03-19 18:02 ` |SUCCESS| pw138482 [PATCH] [v2] app/test-crypto-perf: add throughput dpdklab
2024-03-19 18:06 ` dpdklab
2024-03-19 18:07 ` dpdklab
2024-03-19 18:11 ` dpdklab
2024-03-19 18:11 ` dpdklab
2024-03-19 18:12 ` dpdklab
2024-03-19 18:12 ` dpdklab
2024-03-19 18:13 ` dpdklab
2024-03-19 18:16 ` dpdklab
2024-03-19 18:17 ` dpdklab
2024-03-19 18:18 ` dpdklab
2024-03-19 18:19 ` dpdklab
2024-03-19 18:21 ` dpdklab
2024-03-19 18:22 ` dpdklab
2024-03-19 18:23 ` dpdklab
2024-03-19 18:26 ` dpdklab
2024-03-19 18:26 ` dpdklab
2024-03-19 18:33 ` dpdklab
2024-03-19 18:38 ` dpdklab
2024-03-19 18:46 ` dpdklab
2024-03-19 18:57 ` dpdklab
2024-03-19 19:20 ` dpdklab
2024-03-19 19:25 ` dpdklab
2024-03-19 19:30 ` dpdklab
2024-03-19 19:31 ` dpdklab
2024-03-19 19:32 ` dpdklab
2024-03-19 19:32 ` dpdklab
2024-03-19 19:33 ` dpdklab
2024-03-19 19:35 ` dpdklab
2024-03-19 19:35 ` dpdklab
2024-03-19 19:36 ` dpdklab
2024-03-19 19:37 ` dpdklab
2024-03-19 19:39 ` dpdklab
2024-03-19 19:42 ` dpdklab
2024-03-19 19:43 ` dpdklab
2024-03-19 19:44 ` dpdklab
2024-03-19 19:45 ` dpdklab
2024-03-19 19:45 ` dpdklab
2024-03-19 19:46 ` dpdklab
2024-03-19 19:47 ` dpdklab
2024-03-19 19:47 ` dpdklab
2024-03-19 19:48 ` dpdklab
2024-03-19 19:48 ` dpdklab
2024-03-19 19:49 ` dpdklab
2024-03-19 19:49 ` dpdklab
2024-03-19 19:49 ` dpdklab
2024-03-19 19:50 ` dpdklab
2024-03-19 19:50 ` dpdklab
2024-03-19 19:50 ` dpdklab
2024-03-19 19:51 ` dpdklab
2024-03-19 19:51 ` dpdklab
2024-03-19 19:51 ` dpdklab
2024-03-19 19:52 ` dpdklab
2024-03-19 19:52 ` dpdklab
2024-03-19 19:53 ` dpdklab
2024-03-19 19:58 ` dpdklab
2024-03-19 19:58 ` dpdklab
2024-03-19 20:00 ` dpdklab
2024-03-19 20:00 ` dpdklab
2024-03-19 20:01 ` dpdklab
2024-03-19 20:02 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:03 ` dpdklab
2024-03-19 20:04 ` dpdklab
2024-03-19 20:04 ` dpdklab
2024-03-19 20:05 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:06 ` dpdklab
2024-03-19 20:08 ` dpdklab
2024-03-19 20:17 ` dpdklab
2024-03-19 20:36 ` dpdklab
2024-03-19 20:38 ` dpdklab
2024-03-19 20:55 ` dpdklab
2024-03-19 21:07 ` dpdklab
2024-03-20 7:04 ` |WARNING| " dpdklab
2024-03-21 7:55 ` |SUCCESS| " dpdklab
2024-03-21 8:49 ` 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=202403191124.42JBOdYF3271444@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).