From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw136092 [PATCH] app/crypto-perf: support TLS record
Date: Wed, 24 Jan 2024 14:27:15 +0800 [thread overview]
Message-ID: <202401240627.40O6RF6t2076750@localhost.localdomain> (raw)
In-Reply-To: <20240124064924.3277434-1-gakhil@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/136092
_Compilation OK_
Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Wed, 24 Jan 2024 12:19:24 +0530
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 30a988126ecee65a890a4b6a52690442024f2554
136092 --> 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-01-24 6:52 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240124064924.3277434-1-gakhil@marvell.com>
2024-01-24 6:27 ` qemudev [this message]
2024-01-24 6:31 ` qemudev
2024-01-24 6:51 ` checkpatch
2024-01-24 7:41 ` 0-day Robot
2024-01-24 8:06 dpdklab
2024-01-24 8:10 dpdklab
2024-01-24 8:14 dpdklab
2024-01-24 8:14 dpdklab
2024-01-24 8:22 dpdklab
2024-01-24 8:31 dpdklab
2024-01-24 8:31 dpdklab
2024-01-24 8:32 dpdklab
2024-01-24 8:45 dpdklab
2024-01-24 8:46 dpdklab
2024-01-24 8:49 dpdklab
2024-01-24 8:50 dpdklab
2024-01-24 8:50 dpdklab
2024-01-24 8:51 dpdklab
2024-01-24 8:52 dpdklab
2024-01-24 8:52 dpdklab
2024-01-24 8:52 dpdklab
2024-01-24 8:53 dpdklab
2024-01-24 8:56 dpdklab
2024-01-24 8:56 dpdklab
2024-01-24 8:56 dpdklab
2024-01-24 8:56 dpdklab
2024-01-24 8:57 dpdklab
2024-01-24 8:57 dpdklab
2024-01-24 8:57 dpdklab
2024-01-24 8:57 dpdklab
2024-01-24 8:57 dpdklab
2024-01-24 8:58 dpdklab
2024-01-24 8:58 dpdklab
2024-01-24 8:58 dpdklab
2024-01-24 8:58 dpdklab
2024-01-24 8:58 dpdklab
2024-01-24 8:58 dpdklab
2024-01-24 8:59 dpdklab
2024-01-24 8:59 dpdklab
2024-01-24 8:59 dpdklab
2024-01-24 8:59 dpdklab
2024-01-24 9:00 dpdklab
2024-01-24 9:00 dpdklab
2024-01-24 9:00 dpdklab
2024-01-24 9:00 dpdklab
2024-01-24 9:00 dpdklab
2024-01-24 9:02 dpdklab
2024-01-24 9:05 dpdklab
2024-01-24 9:06 dpdklab
2024-01-24 9:08 dpdklab
2024-01-24 9:09 dpdklab
2024-01-24 9:14 dpdklab
2024-01-24 9:18 dpdklab
2024-01-24 9:19 dpdklab
2024-01-24 9:22 dpdklab
2024-01-24 9:43 dpdklab
2024-01-24 9:52 dpdklab
2024-01-24 10:06 dpdklab
2024-01-24 10:25 dpdklab
2024-01-24 10:48 dpdklab
2024-01-24 11:34 dpdklab
2024-01-24 11:35 dpdklab
2024-01-24 19:16 dpdklab
2024-01-24 20:50 dpdklab
2024-01-24 20:53 dpdklab
2024-01-24 20:53 dpdklab
2024-01-24 20:58 dpdklab
2024-01-24 20:58 dpdklab
2024-01-24 21:01 dpdklab
2024-01-24 21:03 dpdklab
2024-01-24 21:05 dpdklab
2024-01-24 21:05 dpdklab
2024-01-24 21:06 dpdklab
2024-01-24 21:07 dpdklab
2024-01-24 21:07 dpdklab
2024-01-24 21:09 dpdklab
2024-01-24 21:09 dpdklab
2024-01-24 21:09 dpdklab
2024-01-24 21:10 dpdklab
2024-01-24 21:11 dpdklab
2024-01-24 21:11 dpdklab
2024-01-24 21:12 dpdklab
2024-01-24 21:12 dpdklab
2024-01-24 21:12 dpdklab
2024-01-24 21:13 dpdklab
2024-01-24 21:14 dpdklab
2024-01-24 21:16 dpdklab
2024-01-24 21:17 dpdklab
2024-01-24 21:17 dpdklab
2024-01-24 21:18 dpdklab
2024-01-24 21:23 dpdklab
2024-01-24 21:25 dpdklab
2024-01-24 21:30 dpdklab
2024-01-24 21:33 dpdklab
2024-01-24 21:33 dpdklab
2024-01-24 21:33 dpdklab
2024-01-24 21:40 dpdklab
2024-01-24 21:42 dpdklab
2024-01-24 21:43 dpdklab
2024-01-24 21:45 dpdklab
2024-01-24 21:47 dpdklab
2024-01-24 21:48 dpdklab
2024-01-24 21:54 dpdklab
2024-01-24 21:55 dpdklab
2024-01-24 23:38 dpdklab
2024-01-25 1:03 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=202401240627.40O6RF6t2076750@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).