From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw154349 [PATCH] more replace memcpy with structure assignment
Date: Thu, 12 Jun 2025 05:10:23 +0200 (CEST) [thread overview]
Message-ID: <20250612031023.218C71252C1@dpdk.org> (raw)
In-Reply-To: <20250612030952.611893-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/154349
_coding style OK_
next prev parent reply other threads:[~2025-06-12 3:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250612030952.611893-1-stephen@networkplumber.org>
2025-06-12 2:35 ` qemudev
2025-06-12 2:39 ` qemudev
2025-06-12 3:10 ` checkpatch [this message]
2025-06-12 3:48 ` |SUCCESS| pw154349 [PATCH] more replace memcpy with structure assign dpdklab
2025-06-12 3:58 ` dpdklab
2025-06-12 4:00 ` dpdklab
2025-06-12 4:00 ` |PENDING| " dpdklab
2025-06-12 4:25 ` |SUCCESS| pw154349 [PATCH] more replace memcpy with structure assignment 0-day Robot
2025-06-12 4:26 ` |SUCCESS| pw154349 [PATCH] more replace memcpy with structure assign dpdklab
2025-06-12 4:27 ` dpdklab
2025-06-12 4:37 ` |PENDING| " dpdklab
2025-06-12 4:43 ` |SUCCESS| " dpdklab
2025-06-12 5:02 ` dpdklab
2025-06-12 5:15 ` |PENDING| " dpdklab
2025-06-12 6:07 ` |SUCCESS| " dpdklab
2025-06-12 6:32 ` |PENDING| " dpdklab
2025-06-12 7:26 ` dpdklab
2025-06-12 8:29 ` |SUCCESS| " dpdklab
2025-06-12 8:31 ` dpdklab
2025-06-12 8:34 ` dpdklab
2025-06-12 8:37 ` dpdklab
2025-06-12 8:40 ` dpdklab
2025-06-12 8:41 ` dpdklab
2025-06-12 8:51 ` |WARNING| " dpdklab
2025-06-12 8:51 ` dpdklab
2025-06-12 8:52 ` dpdklab
2025-06-12 8:53 ` dpdklab
2025-06-12 8:53 ` dpdklab
2025-06-12 8:53 ` dpdklab
2025-06-12 8:54 ` dpdklab
2025-06-12 8:54 ` dpdklab
2025-06-12 8:56 ` dpdklab
2025-06-12 9:35 ` |SUCCESS| " dpdklab
2025-06-12 10:27 ` dpdklab
2025-06-12 13:24 ` 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=20250612031023.218C71252C1@dpdk.org \
--to=checkpatch@dpdk.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).