From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124520 [PATCH] app/testeventdev: add cipher alg option for cryptodev
Date: Fri, 24 Feb 2023 22:00:44 +0800 [thread overview]
Message-ID: <202302241400.31OE0iM33637163@localhost.localdomain> (raw)
In-Reply-To: <20230224141144.24558-1-asasidharan@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124520
_Compilation OK_
Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Fri, 24 Feb 2023 19:41:43 +0530
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: 094a44c8cab4decbed248f1e866526ebf07a1640
124520 --> 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-24 14:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230224141144.24558-1-asasidharan@marvell.com>
2023-02-24 14:00 ` qemudev [this message]
2023-02-24 14:04 ` qemudev
2023-02-24 14:12 ` checkpatch
2023-02-24 16:39 ` 0-day Robot
2023-02-24 14:38 dpdklab
2023-02-24 14:41 dpdklab
2023-02-24 14:42 dpdklab
2023-02-24 14:47 dpdklab
2023-02-24 14:48 dpdklab
2023-02-24 14:51 dpdklab
2023-02-24 14:54 dpdklab
2023-02-24 14:55 dpdklab
2023-02-24 14:58 dpdklab
2023-02-24 15:03 dpdklab
2023-02-24 16:08 dpdklab
2023-02-24 16:13 dpdklab
2023-02-24 16:14 dpdklab
2023-02-24 16:20 dpdklab
2023-02-24 16:21 dpdklab
2023-02-24 16:23 dpdklab
2023-02-24 16:24 dpdklab
2023-02-24 16:24 dpdklab
2023-02-24 16:29 dpdklab
2023-02-24 16:30 dpdklab
2023-02-24 16:34 dpdklab
2023-02-24 16:43 dpdklab
2023-02-24 16:44 dpdklab
2023-02-24 16:45 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=202302241400.31OE0iM33637163@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).