From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123580 [PATCH v2] test: add cryptodev crosscheck suite
Date: Thu, 9 Feb 2023 20:28:17 +0800 [thread overview]
Message-ID: <202302091228.319CSH6F319131@localhost.localdomain> (raw)
In-Reply-To: <20230209123402.1993179-1-vfialko@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123580
_Compilation OK_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Thu, 9 Feb 2023 13:34:02 +0100
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: a0c837ad1fb5b6a8b10a284ffeb5f9e31bd8ff00
123580 --> 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-02-09 12:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230209123402.1993179-1-vfialko@marvell.com>
2023-02-09 12:28 ` qemudev [this message]
2023-02-09 12:32 ` qemudev
2023-02-09 12:35 ` checkpatch
2023-02-09 13:39 ` |FAILURE| " 0-day Robot
2023-02-17 11:42 |SUCCESS| pw123580 [PATCH] [v2] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-09 13:24 dpdklab
2023-02-09 13:22 dpdklab
2023-02-09 13:20 dpdklab
2023-02-09 13:18 dpdklab
2023-02-09 13:16 dpdklab
2023-02-09 13:15 dpdklab
2023-02-09 13:13 dpdklab
2023-02-09 13:12 dpdklab
2023-02-09 13:07 dpdklab
2023-02-09 13:06 dpdklab
2023-02-09 13:06 dpdklab
2023-02-09 13:05 dpdklab
2023-02-09 13:01 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=202302091228.319CSH6F319131@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).