From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148913 [PATCH v2] crypto/virtio: remove redundant crypto queue free
Date: Wed, 27 Nov 2024 21:47:25 +0800 [thread overview]
Message-ID: <202411271347.4ARDlPEu958840@localhost.localdomain> (raw)
In-Reply-To: <20241127141248.1078678-1-rmudimadugul@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148913
_Compilation OK_
Submitter: Rajesh Mudimadugula <rmudimadugul@marvell.com>
Date: Wed, 27 Nov 2024 14:12:48 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: f4ccce58c1a33cb41e1e820da504698437987efc
148913 --> 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: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241127141248.1078678-1-rmudimadugul@marvell.com>
2024-11-27 13:47 ` qemudev [this message]
2024-11-27 13:52 ` qemudev
2024-11-27 14:13 ` checkpatch
2024-11-27 15:23 ` 0-day Robot
2024-11-27 16:03 ` |PENDING| pw148913 [PATCH] [v2] crypto/virtio: remove redundant cryp dpdklab
2024-11-27 16:05 ` dpdklab
2024-11-27 16:10 ` dpdklab
2024-11-27 16:11 ` |SUCCESS| " dpdklab
2024-11-27 16:13 ` |PENDING| " dpdklab
2024-11-27 16:19 ` |SUCCESS| " dpdklab
2024-11-27 16:24 ` dpdklab
2024-11-27 16:45 ` dpdklab
2024-11-27 17:17 ` dpdklab
2024-11-27 17:34 ` dpdklab
2024-11-27 17:54 ` |WARNING| " dpdklab
2024-11-27 18:05 ` |SUCCESS| " dpdklab
2024-11-27 18:29 ` dpdklab
2024-11-27 18:33 ` dpdklab
2024-11-27 19:09 ` dpdklab
2024-11-29 8:05 ` |SUCCESS| pw148913 [PATCH v2] crypto/virtio: remove redundant crypto queue free qemudev
2024-11-29 8:06 ` qemudev
2024-11-29 10:22 ` qemudev
2024-11-29 10:22 ` 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=202411271347.4ARDlPEu958840@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).