automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133682 [PATCH v2] crypto/qat: add sm2 ecdsa
Date: Wed, 1 Nov 2023 05:11:08 +0800	[thread overview]
Message-ID: <202310312111.39VLB8kt237465@localhost.localdomain> (raw)
In-Reply-To: <20231031212632.6663-1-arkadiuszx.kusztal@intel.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/133682

_Compilation OK_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Tue, 31 Oct 2023 21:26:32 +0000
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 37a1d321840d2a9bde0f9b3a58dfae96b45f34c0

133682 --> 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


       reply	other threads:[~2023-10-31 21:32 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231031212632.6663-1-arkadiuszx.kusztal@intel.com>
2023-10-31 21:11 ` qemudev [this message]
2023-10-31 21:15 ` qemudev
2023-10-31 21:27 ` |WARNING| " checkpatch
2023-10-31 22:39 ` |SUCCESS| " 0-day Robot
2023-10-31 23:35 |SUCCESS| pw133682 [PATCH] [v2] " dpdklab
2023-10-31 23:37 dpdklab
2023-10-31 23:37 dpdklab
2023-10-31 23:37 dpdklab
2023-10-31 23:38 dpdklab
2023-10-31 23:39 dpdklab
2023-10-31 23:39 dpdklab
2023-10-31 23:39 dpdklab
2023-10-31 23:40 dpdklab
2023-10-31 23:40 dpdklab
2023-10-31 23:40 dpdklab
2023-10-31 23:40 dpdklab
2023-10-31 23:41 dpdklab
2023-10-31 23:41 dpdklab
2023-10-31 23:41 dpdklab
2023-10-31 23:41 dpdklab
2023-10-31 23:42 dpdklab
2023-10-31 23:43 dpdklab
2023-10-31 23:43 dpdklab
2023-10-31 23:43 dpdklab
2023-10-31 23:43 dpdklab
2023-10-31 23:44 dpdklab
2023-10-31 23:44 dpdklab
2023-10-31 23:44 dpdklab
2023-10-31 23:44 dpdklab
2023-10-31 23:44 dpdklab
2023-10-31 23:44 dpdklab
2023-10-31 23:45 dpdklab
2023-10-31 23:45 dpdklab
2023-10-31 23:45 dpdklab
2023-10-31 23:45 dpdklab
2023-10-31 23:45 dpdklab
2023-10-31 23:46 dpdklab
2023-10-31 23:46 dpdklab
2023-10-31 23:47 dpdklab
2023-10-31 23:47 dpdklab
2023-10-31 23:47 dpdklab
2023-10-31 23:50 dpdklab
2023-10-31 23:51 dpdklab
2023-10-31 23:52 dpdklab
2023-10-31 23:53 dpdklab
2023-10-31 23:54 dpdklab
2023-11-01  0:11 dpdklab
2023-11-01  0:13 dpdklab
2023-11-01  0:22 dpdklab
2023-11-01  0:25 dpdklab
2023-11-01  0:28 dpdklab
2023-11-01  0:34 dpdklab
2023-11-01  0:43 dpdklab
2023-11-01  0:47 dpdklab
2023-11-01  1:11 dpdklab
2023-11-01  1:13 dpdklab
2023-11-01  1:16 dpdklab
2023-11-01  2:02 dpdklab
2023-11-01  2:06 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=202310312111.39VLB8kt237465@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).