From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139873 [PATCH v2] common/qat: add legacy algorithm option
Date: Mon, 6 May 2024 02:06:31 +0800 [thread overview]
Message-ID: <202405051806.445I6VHU1408099@localhost.localdomain> (raw)
In-Reply-To: <20240505183142.20148-1-arkadiuszx.kusztal@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139873
_Compilation OK_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Sun, 5 May 2024 19:31:42 +0100
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139873 --> 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-05-05 18:34 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240505183142.20148-1-arkadiuszx.kusztal@intel.com>
2024-05-05 18:06 ` qemudev [this message]
2024-05-05 18:11 ` qemudev
2024-05-05 19:16 ` |SUCCESS| pw139873 [PATCH] [v2] common/qat: add legacy algorithm opt dpdklab
2024-05-05 19:17 ` dpdklab
2024-05-05 19:17 ` dpdklab
2024-05-05 19:17 ` dpdklab
2024-05-05 19:18 ` dpdklab
2024-05-05 19:18 ` dpdklab
2024-05-05 19:18 ` dpdklab
2024-05-05 19:19 ` dpdklab
2024-05-05 19:19 ` dpdklab
2024-05-05 19:19 ` dpdklab
2024-05-05 19:19 ` dpdklab
2024-05-05 19:19 ` dpdklab
2024-05-05 19:20 ` dpdklab
2024-05-05 19:20 ` dpdklab
2024-05-05 19:20 ` dpdklab
2024-05-05 19:20 ` dpdklab
2024-05-05 19:20 ` dpdklab
2024-05-05 19:21 ` dpdklab
2024-05-05 19:21 ` dpdklab
2024-05-05 19:21 ` dpdklab
2024-05-05 19:21 ` dpdklab
2024-05-05 19:22 ` dpdklab
2024-05-05 19:22 ` dpdklab
2024-05-05 19:22 ` dpdklab
2024-05-05 19:22 ` dpdklab
2024-05-05 19:22 ` dpdklab
2024-05-05 19:22 ` dpdklab
2024-05-05 19:22 ` dpdklab
2024-05-05 19:23 ` dpdklab
2024-05-05 19:23 ` dpdklab
2024-05-05 19:23 ` dpdklab
2024-05-05 19:23 ` |SUCCESS| pw139873 [PATCH v2] common/qat: add legacy algorithm option 0-day Robot
2024-05-05 19:23 ` |SUCCESS| pw139873 [PATCH] [v2] common/qat: add legacy algorithm opt dpdklab
2024-05-05 19:23 ` dpdklab
2024-05-05 19:24 ` dpdklab
2024-05-05 19:24 ` dpdklab
2024-05-05 19:24 ` dpdklab
2024-05-05 19:25 ` dpdklab
2024-05-05 19:25 ` dpdklab
2024-05-05 19:26 ` dpdklab
2024-05-05 19:26 ` dpdklab
2024-05-05 19:27 ` dpdklab
2024-05-05 19:28 ` dpdklab
2024-05-05 19:28 ` dpdklab
2024-05-05 19:28 ` dpdklab
2024-05-05 19:29 ` dpdklab
2024-05-05 19:29 ` dpdklab
2024-05-05 19:30 ` dpdklab
2024-05-05 19:30 ` dpdklab
2024-05-05 19:31 ` dpdklab
2024-05-05 19:33 ` dpdklab
2024-05-05 19:34 ` dpdklab
2024-05-05 19:35 ` dpdklab
2024-05-05 19:35 ` dpdklab
2024-05-05 19:35 ` dpdklab
2024-05-05 19:36 ` dpdklab
2024-05-05 19:37 ` dpdklab
2024-05-05 19:38 ` dpdklab
2024-05-05 19:38 ` dpdklab
2024-05-05 19:38 ` dpdklab
2024-05-05 19:39 ` dpdklab
2024-05-05 19:39 ` dpdklab
2024-05-05 19:40 ` dpdklab
2024-05-05 19:40 ` dpdklab
2024-05-05 19:41 ` dpdklab
2024-05-05 19:42 ` dpdklab
2024-05-05 19:42 ` dpdklab
2024-05-05 19:44 ` dpdklab
2024-05-05 19:46 ` dpdklab
2024-05-05 19:49 ` dpdklab
2024-05-05 19:51 ` dpdklab
2024-05-05 19:51 ` dpdklab
2024-05-05 19:51 ` dpdklab
2024-05-05 19:54 ` dpdklab
2024-05-05 19:57 ` dpdklab
2024-05-05 19:58 ` dpdklab
2024-05-05 19:58 ` dpdklab
2024-05-05 20:00 ` dpdklab
2024-05-05 20:01 ` dpdklab
2024-05-05 20:07 ` dpdklab
2024-05-05 20:14 ` dpdklab
2024-05-05 20:15 ` dpdklab
2024-05-05 20:16 ` dpdklab
2024-05-05 20:27 ` dpdklab
2024-05-05 21:54 ` dpdklab
2024-05-06 15:16 ` dpdklab
2024-05-06 18:51 ` |SUCCESS| pw139873 [PATCH v2] common/qat: add legacy algorithm option checkpatch
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=202405051806.445I6VHU1408099@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).