From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw157266-157267 [PATCH v2 3/3] app/compress-perf: support for dictionaries and PDCP checksum
Date: Sat, 4 Oct 2025 00:17:25 +0800 [thread overview]
Message-ID: <202510031617.593GHPha109655@localhost.localdomain> (raw)
In-Reply-To: <20251003165132.3201643-3-svaze@qti.qualcomm.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/157267
_Compilation OK_
Submitter: Sameer Vaze <svaze@qti.qualcomm.com>
Date: Fri, 3 Oct 2025 10:51:30 -0600
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: caa17cb4b057a31ee04067459fe543f7d7ae1079
157266-157267 --> 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:[~2025-10-03 16:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251003165132.3201643-3-svaze@qti.qualcomm.com>
2025-10-03 16:17 ` qemudev [this message]
2025-10-03 16:22 ` qemudev
2025-10-03 16:53 ` |SUCCESS| pw157267 " checkpatch
2025-10-03 17:19 ` |PENDING| pw157266-157267 [PATCH] [v2,3/3] app/compress-perf: suppor dpdklab
2025-10-03 17:22 ` dpdklab
2025-10-03 17:23 ` |SUCCESS| " dpdklab
2025-10-03 17:27 ` dpdklab
2025-10-03 17:31 ` |PENDING| " dpdklab
2025-10-03 17:32 ` dpdklab
2025-10-03 17:40 ` |SUCCESS| " dpdklab
2025-10-03 17:43 ` dpdklab
2025-10-03 17:44 ` dpdklab
2025-10-03 17:45 ` dpdklab
2025-10-03 17:56 ` dpdklab
2025-10-03 17:57 ` dpdklab
2025-10-03 18:02 ` dpdklab
2025-10-03 18:03 ` dpdklab
2025-10-03 18:06 ` |SUCCESS| pw157267 [PATCH v2 3/3] app/compress-perf: support for dictionaries and PDCP checksum 0-day Robot
2025-10-03 18:06 ` 0-day Robot
2025-10-03 18:07 ` |SUCCESS| pw157266-157267 [PATCH] [v2,3/3] app/compress-perf: suppor 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=202510031617.593GHPha109655@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).