From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw157576 [PATCH] app/crypto-perf: add ECDSA P192/P224/P521 support
Date: Wed, 15 Oct 2025 14:02:48 +0800 [thread overview]
Message-ID: <202510150602.59F62mg8114665@localhost.localdomain> (raw)
In-Reply-To: <20251015062758.1096015-1-rchiluka@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/157576
_Compilation OK_
Submitter: Rupesh Chiluka <rchiluka@marvell.com>
Date: Wed, 15 Oct 2025 11:57:58 +0530
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 2aa7141a4e2c78e3cce03dbd613532a2166123c1
157576 --> 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:[~2025-10-15 6:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251015062758.1096015-1-rchiluka@marvell.com>
2025-10-15 6:02 ` qemudev [this message]
2025-10-15 6:07 ` qemudev
2025-10-15 6:29 ` checkpatch
2025-10-15 6:53 ` |PENDING| pw157576 [PATCH] app/crypto-perf: add ECDSA P192/P224/P521 dpdklab
2025-10-15 6:54 ` |SUCCESS| " dpdklab
2025-10-15 6:56 ` |PENDING| " dpdklab
2025-10-15 6:58 ` |SUCCESS| " dpdklab
2025-10-15 7:03 ` |PENDING| " dpdklab
2025-10-15 7:07 ` dpdklab
2025-10-15 7:14 ` |SUCCESS| " dpdklab
2025-10-15 7:16 ` |PENDING| " dpdklab
2025-10-15 7:16 ` |SUCCESS| " dpdklab
2025-10-15 7:16 ` dpdklab
2025-10-15 7:16 ` dpdklab
2025-10-15 7:21 ` dpdklab
2025-10-15 7:35 ` dpdklab
2025-10-15 7:36 ` dpdklab
2025-10-15 7:37 ` dpdklab
2025-10-15 7:46 ` dpdklab
2025-10-15 7:48 ` dpdklab
2025-10-15 13:04 ` dpdklab
2025-10-15 13:05 ` dpdklab
2025-10-15 15:29 ` 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=202510150602.59F62mg8114665@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).