From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw157854 [PATCH v3 1/1] lib/eal/riscv: optimize rte_memcpy with RISCV vector and zicbop extensions
Date: Mon, 20 Oct 2025 09:30:19 -0400 [thread overview]
Message-ID: <20251020133019.2635963-1-robot@bytheb.org> (raw)
In-Reply-To: <20251020120832.1377782-2-chen.qiguo@zte.com.cn>
From: robot@bytheb.org
Test-Label: github-robot-post
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/157854/
_github post: success_
HTML Link: https://github.com/ovsrobot/dpdk/pull/216
next prev parent reply other threads:[~2025-10-20 13:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251020120832.1377782-2-chen.qiguo@zte.com.cn>
2025-10-20 11:49 ` qemudev
2025-10-20 11:54 ` qemudev
2025-10-20 12:24 ` checkpatch
2025-10-20 12:54 ` |PENDING| pw157854 [PATCH] [v3,1/1] lib/eal/riscv: optimize rte_memc dpdklab
2025-10-20 12:58 ` |SUCCESS| " dpdklab
2025-10-20 13:02 ` dpdklab
2025-10-20 13:17 ` dpdklab
2025-10-20 13:20 ` dpdklab
2025-10-20 13:30 ` |SUCCESS| pw157854 [PATCH v3 1/1] lib/eal/riscv: optimize rte_memcpy with RISCV vector and zicbop extensions 0-day Robot
2025-10-20 13:30 ` 0-day Robot [this message]
2025-10-20 13:31 ` |SUCCESS| pw157854 [PATCH] [v3,1/1] lib/eal/riscv: optimize rte_memc dpdklab
2025-10-20 13:39 ` |PENDING| " dpdklab
2025-10-20 13:51 ` |SUCCESS| " dpdklab
2025-10-20 13:51 ` dpdklab
2025-10-20 13:52 ` |PENDING| " dpdklab
2025-10-20 14:05 ` dpdklab
2025-10-20 14:32 ` |SUCCESS| " dpdklab
2025-10-20 14:33 ` dpdklab
2025-10-20 14:55 ` dpdklab
2025-10-20 15:02 ` |WARNING| " dpdklab
2025-10-20 15:02 ` |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=20251020133019.2635963-1-robot@bytheb.org \
--to=robot@bytheb.org \
--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).