From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148944 [PATCH] crypto/openssl: fix CMAC auth context update
Date: Sat, 30 Nov 2024 03:57:51 +0800 [thread overview]
Message-ID: <202411291957.4ATJvppg3946919@localhost.localdomain> (raw)
In-Reply-To: <20241129202023.1203341-1-wathsala.vithanage@arm.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148944
_Compilation OK_
Submitter: Wathsala Vithanage <wathsala.vithanage@arm.com>
Date: Fri, 29 Nov 2024 20:20:22 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 4843aacb0d1201fef37e8a579fcd8baec4acdf98
148944 --> 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-11-29 20:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241129202023.1203341-1-wathsala.vithanage@arm.com>
2024-11-29 19:57 ` qemudev [this message]
2024-11-29 20:02 ` qemudev
2024-11-29 20:21 ` checkpatch
2024-11-29 21:23 ` 0-day Robot
2024-11-29 22:02 ` |SUCCESS| pw148944 [PATCH] crypto/openssl: fix CMAC auth context upd dpdklab
2024-11-29 22:08 ` dpdklab
2024-11-29 22:14 ` dpdklab
2024-11-29 22:43 ` dpdklab
2024-11-29 22:51 ` |PENDING| " dpdklab
2024-11-29 22:58 ` dpdklab
2024-11-29 23:04 ` |SUCCESS| " dpdklab
2024-11-29 23:05 ` dpdklab
2024-11-29 23:08 ` dpdklab
2024-11-29 23:31 ` dpdklab
2024-11-29 23:44 ` |WARNING| " dpdklab
2024-11-30 0:07 ` |SUCCESS| " dpdklab
2024-11-30 0:15 ` |WARNING| " dpdklab
2024-11-30 0:26 ` dpdklab
2024-11-30 0:31 ` |SUCCESS| " 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=202411291957.4ATJvppg3946919@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).