From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148015 [PATCH v3] crypto/qat: fix ecdsa session handling
Date: Wed, 6 Nov 2024 22:43:23 +0800 [thread overview]
Message-ID: <202411061443.4A6EhNnZ769907@localhost.localdomain> (raw)
In-Reply-To: <20241106151421.2722-1-arkadiuszx.kusztal@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148015
_Compilation OK_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wed, 6 Nov 2024 15:14:21 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 5855c0051013b8162280c07985baa543bce067c0
148015 --> 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-11-06 15:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241106151421.2722-1-arkadiuszx.kusztal@intel.com>
2024-11-06 14:43 ` qemudev [this message]
2024-11-06 14:48 ` qemudev
2024-11-06 15:15 ` checkpatch
2024-11-06 15:50 ` |PENDING| pw148015 [PATCH] [v3] crypto/qat: fix ecdsa session handli dpdklab
2024-11-06 15:52 ` dpdklab
2024-11-06 15:59 ` dpdklab
2024-11-06 16:00 ` |SUCCESS| " dpdklab
2024-11-06 16:02 ` dpdklab
2024-11-06 16:03 ` dpdklab
2024-11-06 16:05 ` |PENDING| " dpdklab
2024-11-06 16:06 ` |SUCCESS| pw148015 [PATCH v3] crypto/qat: fix ecdsa session handling 0-day Robot
2024-11-06 16:12 ` |SUCCESS| pw148015 [PATCH] [v3] crypto/qat: fix ecdsa session handli dpdklab
2024-11-06 16:18 ` dpdklab
2024-11-06 16:19 ` dpdklab
2024-11-06 16:25 ` dpdklab
2024-11-06 16:36 ` dpdklab
2024-11-06 16:50 ` dpdklab
2024-11-06 17:01 ` dpdklab
2024-11-06 19:58 ` dpdklab
2024-11-07 9:24 ` 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=202411061443.4A6EhNnZ769907@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).