From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147479-147491 [PATCH v18 15/15] app/test: add cryptodev test for zsda
Date: Mon, 28 Oct 2024 15:47:52 +0800 [thread overview]
Message-ID: <202410280747.49S7lqg02839544@localhost.localdomain> (raw)
In-Reply-To: <20241028081218.2435034-14-li.hanxiao@zte.com.cn>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/147491
_Compilation OK_
Submitter: Hanxiao Li <li.hanxiao@zte.com.cn>
Date: Mon, 28 Oct 2024 16:09:19 +0800
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 3ee7a3e0e0e0f5a81a4b102a834697bc488fb32f
147479-147491 --> 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-10-28 8:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241028081218.2435034-14-li.hanxiao@zte.com.cn>
2024-10-28 7:47 ` qemudev [this message]
2024-10-28 7:52 ` qemudev
2024-10-28 8:20 ` |SUCCESS| pw147491 " checkpatch
2024-10-28 9:05 ` 0-day Robot
2024-10-31 20:18 ` |PENDING| pw147479-147491 [PATCH] [v18,15/15] app/test: add cryptode dpdklab
2024-10-31 20:32 ` |SUCCESS| " dpdklab
2024-10-31 20:34 ` |PENDING| " dpdklab
2024-10-31 20:35 ` |SUCCESS| " dpdklab
2024-11-01 0:20 ` dpdklab
2024-11-01 0:59 ` |PENDING| " dpdklab
2024-11-01 1:04 ` |SUCCESS| " dpdklab
2024-11-01 1:13 ` dpdklab
2024-11-01 1:26 ` dpdklab
2024-11-01 2:32 ` dpdklab
2024-11-01 5:42 ` |PENDING| " dpdklab
2024-11-01 6:57 ` |SUCCESS| " dpdklab
2024-11-01 8:08 ` dpdklab
2024-11-01 11:26 ` dpdklab
2024-11-01 18:53 ` dpdklab
2024-11-02 3:07 ` dpdklab
2024-11-02 3:42 ` dpdklab
2024-11-02 13:32 ` dpdklab
2024-11-02 20:14 ` dpdklab
2024-11-03 0:37 ` dpdklab
2024-11-03 0:39 ` dpdklab
2024-11-05 23:37 ` 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=202410280747.49S7lqg02839544@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).