From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138331 [PATCH] app/crypto-perf-test: fix unset crc algorithm
Date: Wed, 13 Mar 2024 22:34:02 +0800 [thread overview]
Message-ID: <202403131434.42DEY2jo175753@localhost.localdomain> (raw)
In-Reply-To: <20240313145448.26264-1-arkadiuszx.kusztal@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138331
_Compilation OK_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wed, 13 Mar 2024 14:54:48 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 197bb4582c43df3c40db97a0da463afea5e74951
138331 --> 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-03-13 14:58 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240313145448.26264-1-arkadiuszx.kusztal@intel.com>
2024-03-13 14:34 ` qemudev [this message]
2024-03-13 14:38 ` qemudev
2024-03-13 14:55 ` checkpatch
2024-03-13 15:38 ` |SUCCESS| pw138331 [PATCH] app/crypto-perf-test: fix unset crc algor dpdklab
2024-03-13 15:39 ` dpdklab
2024-03-13 15:39 ` dpdklab
2024-03-13 15:39 ` dpdklab
2024-03-13 15:39 ` dpdklab
2024-03-13 15:40 ` dpdklab
2024-03-13 15:40 ` dpdklab
2024-03-13 15:40 ` dpdklab
2024-03-13 15:40 ` dpdklab
2024-03-13 15:41 ` dpdklab
2024-03-13 15:41 ` dpdklab
2024-03-13 15:41 ` dpdklab
2024-03-13 15:42 ` dpdklab
2024-03-13 15:42 ` dpdklab
2024-03-13 15:42 ` dpdklab
2024-03-13 15:43 ` dpdklab
2024-03-13 15:43 ` dpdklab
2024-03-13 15:43 ` dpdklab
2024-03-13 15:43 ` |SUCCESS| pw138331 [PATCH] app/crypto-perf-test: fix unset crc algorithm 0-day Robot
2024-03-13 15:43 ` |SUCCESS| pw138331 [PATCH] app/crypto-perf-test: fix unset crc algor dpdklab
2024-03-13 15:44 ` dpdklab
2024-03-13 15:44 ` dpdklab
2024-03-13 15:45 ` dpdklab
2024-03-13 15:45 ` dpdklab
2024-03-13 15:45 ` dpdklab
2024-03-13 15:45 ` dpdklab
2024-03-13 15:46 ` dpdklab
2024-03-13 15:46 ` dpdklab
2024-03-13 15:46 ` dpdklab
2024-03-13 15:47 ` dpdklab
2024-03-13 15:47 ` dpdklab
2024-03-13 15:47 ` dpdklab
2024-03-13 15:47 ` dpdklab
2024-03-13 15:48 ` |FAILURE| " dpdklab
2024-03-13 15:48 ` |SUCCESS| " dpdklab
2024-03-13 15:48 ` |FAILURE| " dpdklab
2024-03-13 15:48 ` |SUCCESS| " dpdklab
2024-03-13 15:49 ` |FAILURE| " dpdklab
2024-03-13 15:49 ` |SUCCESS| " dpdklab
2024-03-13 15:49 ` dpdklab
2024-03-13 15:49 ` dpdklab
2024-03-13 15:49 ` dpdklab
2024-03-13 15:50 ` dpdklab
2024-03-13 15:50 ` |FAILURE| " dpdklab
2024-03-13 15:50 ` dpdklab
2024-03-13 15:51 ` |SUCCESS| " dpdklab
2024-03-13 15:51 ` dpdklab
2024-03-13 15:51 ` |FAILURE| " dpdklab
2024-03-13 15:51 ` |SUCCESS| " dpdklab
2024-03-13 15:51 ` dpdklab
2024-03-13 15:52 ` dpdklab
2024-03-13 15:52 ` |FAILURE| " dpdklab
2024-03-13 15:52 ` |SUCCESS| " dpdklab
2024-03-13 15:52 ` dpdklab
2024-03-13 15:52 ` dpdklab
2024-03-13 15:53 ` |FAILURE| " dpdklab
2024-03-13 15:53 ` dpdklab
2024-03-13 15:53 ` |SUCCESS| " dpdklab
2024-03-13 15:53 ` dpdklab
2024-03-13 15:53 ` dpdklab
2024-03-13 15:53 ` |FAILURE| " dpdklab
2024-03-13 15:53 ` |SUCCESS| " dpdklab
2024-03-13 15:54 ` |FAILURE| " dpdklab
2024-03-13 15:55 ` dpdklab
2024-03-13 15:55 ` |SUCCESS| " dpdklab
2024-03-13 15:56 ` dpdklab
2024-03-13 15:57 ` dpdklab
2024-03-13 15:57 ` dpdklab
2024-03-13 16:01 ` dpdklab
2024-03-13 16:04 ` dpdklab
2024-03-13 16:04 ` |FAILURE| " dpdklab
2024-03-13 16:04 ` |SUCCESS| " dpdklab
2024-03-13 16:05 ` dpdklab
2024-03-13 17:05 ` dpdklab
2024-03-17 5:23 ` dpdklab
2024-03-17 5:52 ` 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=202403131434.42DEY2jo175753@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).