From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw157354 [PATCH] eal/riscv: optimize memcpy for small copies under 64 bytes
Date: Thu, 9 Oct 2025 14:05:28 +0800 [thread overview]
Message-ID: <202510090605.59965Soj2004030@localhost.localdomain> (raw)
In-Reply-To: <20251009063030.2776794-1-sunyuechi@iscas.ac.cn>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/157354
_Compilation OK_
Submitter: Sun Yuechi <sunyuechi@iscas.ac.cn>
Date: Thu, 9 Oct 2025 14:30:30 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 2b403dd8fb37d0ba13723e44ffc7ee2c2795f838
157354 --> 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-09 6:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251009063030.2776794-1-sunyuechi@iscas.ac.cn>
2025-10-09 6:05 ` qemudev [this message]
2025-10-09 6:10 ` qemudev
2025-10-09 6:32 ` checkpatch
2025-10-09 7:00 ` |PENDING| pw157354 [PATCH] eal/riscv: optimize memcpy for small copi dpdklab
2025-10-09 7:01 ` dpdklab
2025-10-09 7:03 ` |SUCCESS| " dpdklab
2025-10-09 7:07 ` dpdklab
2025-10-09 7:09 ` |PENDING| " dpdklab
2025-10-09 7:11 ` dpdklab
2025-10-09 7:20 ` |SUCCESS| " dpdklab
2025-10-09 7:22 ` dpdklab
2025-10-09 7:24 ` dpdklab
2025-10-09 7:35 ` |SUCCESS| pw157354 [PATCH] eal/riscv: optimize memcpy for small copies under 64 bytes 0-day Robot
2025-10-09 7:35 ` 0-day Robot
2025-10-09 7:36 ` |SUCCESS| pw157354 [PATCH] eal/riscv: optimize memcpy for small copi dpdklab
2025-10-09 7:41 ` dpdklab
2025-10-09 7:42 ` dpdklab
2025-10-09 7:43 ` dpdklab
2025-10-09 7:51 ` dpdklab
2025-10-09 8:01 ` dpdklab
2025-10-09 8:07 ` 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=202510090605.59965Soj2004030@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).