From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw131514 [PATCH] crypto/qat: add sm2 ecdsa
Date: Sun, 17 Sep 2023 23:25:08 +0800 [thread overview]
Message-ID: <202309171525.38HFP8MM3930923@localhost.localdomain> (raw)
In-Reply-To: <20230917154449.3509865-1-arkadiuszx.kusztal@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/131514
_Compilation OK_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Sun, 17 Sep 2023 15:44:49 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 62895ec564de9e6929bda6e19b1e974f36c2d482
131514 --> 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:[~2023-09-17 15:46 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230917154449.3509865-1-arkadiuszx.kusztal@intel.com>
2023-09-17 15:25 ` qemudev [this message]
2023-09-17 15:29 ` qemudev
2023-09-17 15:46 ` |WARNING| " checkpatch
2023-09-17 16:39 ` |SUCCESS| " 0-day Robot
2023-09-17 17:34 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-09-17 16:52 dpdklab
2023-09-17 16:43 dpdklab
2023-09-17 16:40 dpdklab
2023-09-17 16:39 dpdklab
2023-09-17 16:37 dpdklab
2023-09-17 16:36 dpdklab
2023-09-17 16:36 dpdklab
2023-09-17 16:36 dpdklab
2023-09-17 16:33 dpdklab
2023-09-17 16:33 dpdklab
2023-09-17 16:32 dpdklab
2023-09-17 16:32 dpdklab
2023-09-17 16:32 dpdklab
2023-09-17 16:29 dpdklab
2023-09-17 16:28 dpdklab
2023-09-17 16:27 dpdklab
2023-09-17 16:25 dpdklab
2023-09-17 16:25 dpdklab
2023-09-17 16:24 dpdklab
2023-09-17 16:24 dpdklab
2023-09-17 16:24 dpdklab
2023-09-17 16:23 dpdklab
2023-09-17 16:22 dpdklab
2023-09-17 16:22 dpdklab
2023-09-17 16:22 dpdklab
2023-09-17 16:22 dpdklab
2023-09-17 16:20 dpdklab
2023-09-17 16:19 dpdklab
2023-09-17 16:19 dpdklab
2023-09-17 16:19 dpdklab
2023-09-17 16:19 dpdklab
2023-09-17 16:18 dpdklab
2023-09-17 16:18 dpdklab
2023-09-17 16:18 dpdklab
2023-09-17 16:18 dpdklab
2023-09-17 16:18 dpdklab
2023-09-17 16:17 dpdklab
2023-09-17 16:16 dpdklab
2023-09-17 16:16 dpdklab
2023-09-17 16:16 dpdklab
2023-09-17 16:15 dpdklab
2023-09-17 16:13 dpdklab
2023-09-17 16:13 dpdklab
2023-09-17 16:13 dpdklab
2023-09-17 16:13 dpdklab
2023-09-17 16:13 dpdklab
2023-09-17 16:12 dpdklab
2023-09-17 16:11 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=202309171525.38HFP8MM3930923@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).