From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148912 [PATCH] crypto/virtio: remove redundant crypto queue free
Date: Wed, 27 Nov 2024 21:02:37 +0800 [thread overview]
Message-ID: <202411271302.4ARD2b8u794576@localhost.localdomain> (raw)
In-Reply-To: <20241127133415.1077670-1-rmudimadugul@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148912
_Compilation OK_
Submitter: Rajesh Mudimadugula <rmudimadugul@marvell.com>
Date: Wed, 27 Nov 2024 13:34:15 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: f4ccce58c1a33cb41e1e820da504698437987efc
148912 --> 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 18:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241127133415.1077670-1-rmudimadugul@marvell.com>
2024-11-27 13:02 ` qemudev [this message]
2024-11-27 13:07 ` qemudev
2024-11-27 13:35 ` checkpatch
2024-11-27 14:13 ` |SUCCESS| pw148912 [PATCH] crypto/virtio: remove redundant crypto qu dpdklab
2024-11-27 14:14 ` |PENDING| " dpdklab
2024-11-27 14:16 ` dpdklab
2024-11-27 14:18 ` |SUCCESS| " dpdklab
2024-11-27 14:27 ` dpdklab
2024-11-27 14:29 ` dpdklab
2024-11-27 14:40 ` dpdklab
2024-11-27 14:46 ` dpdklab
2024-11-27 14:54 ` dpdklab
2024-11-27 15:00 ` dpdklab
2024-11-27 15:03 ` dpdklab
2024-11-27 15:04 ` dpdklab
2024-11-27 16:30 ` dpdklab
2024-11-29 8:06 ` |SUCCESS| pw148912 [PATCH] crypto/virtio: remove redundant crypto queue free qemudev
2024-11-29 8:07 ` qemudev
2024-11-29 10:23 ` qemudev
2024-11-29 10:23 ` qemudev
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=202411271302.4ARD2b8u794576@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).