automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121891-121893 [PATCH v2 3/3] crypto/cnxk: add support for SHAKE hash
Date: Thu, 12 Jan 2023 18:42:01 +0800	[thread overview]
Message-ID: <202301121042.30CAg1DE3071153@localhost.localdomain> (raw)
In-Reply-To: <20230112104733.1835722-4-vfialko@marvell.com>

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

_Compilation OK_

Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Thu, 12 Jan 2023 11:47:31 +0100
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 83397b9f073904438965e1fda2efe76f7850fe01

121891-121893 --> 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-01-12 10:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230112104733.1835722-4-vfialko@marvell.com>
2023-01-12 10:42 ` qemudev [this message]
2023-01-12 10:46 ` qemudev
2023-01-12 10:49 ` |SUCCESS| pw121893 " checkpatch
2023-01-12 11:59 ` 0-day Robot
2023-01-12 11:21 |SUCCESS| pw121891-121893 [PATCH] [v2, " dpdklab
2023-01-12 11:24 dpdklab
2023-01-12 11:26 dpdklab
2023-01-12 11:27 dpdklab
2023-01-12 11:29 dpdklab
2023-01-12 11:34 dpdklab
2023-01-12 11:37 dpdklab
2023-01-12 11:41 dpdklab
2023-01-12 13:30 dpdklab
2023-01-12 17:42 dpdklab
2023-01-12 18:03 dpdklab
2023-01-12 18:05 dpdklab
2023-01-12 18:05 dpdklab
2023-01-12 18:12 dpdklab
2023-01-12 18:12 dpdklab
2023-01-12 18:43 dpdklab
2023-01-12 18:43 dpdklab
2023-01-12 18:43 dpdklab
2023-01-12 18:53 dpdklab
2023-01-12 19:13 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=202301121042.30CAg1DE3071153@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).