From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw139126 [PATCH v4] eal/x86: improve rte_memcpy const size 16 performance
Date: Fri, 5 Apr 2024 15:50:05 +0200 (CEST) [thread overview]
Message-ID: <20240405135005.38292121EEE@dpdk.org> (raw)
In-Reply-To: <20240405134831.47996-1-mb@smartsharesystems.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/139126
_coding style OK_
next prev parent reply other threads:[~2024-04-05 13:50 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240405134831.47996-1-mb@smartsharesystems.com>
2024-04-05 13:25 ` qemudev
2024-04-05 13:30 ` qemudev
2024-04-05 13:50 ` checkpatch [this message]
2024-04-05 14:29 ` |SUCCESS| pw139126 [PATCH] [v4] eal/x86: improve rte_memcpy const si dpdklab
2024-04-05 14:29 ` dpdklab
2024-04-05 14:30 ` dpdklab
2024-04-05 14:31 ` dpdklab
2024-04-05 14:44 ` |SUCCESS| pw139126 [PATCH v4] eal/x86: improve rte_memcpy const size 16 performance 0-day Robot
2024-04-05 14:48 ` |SUCCESS| pw139126 [PATCH] [v4] eal/x86: improve rte_memcpy const si dpdklab
2024-04-05 14:48 ` dpdklab
2024-04-05 14:48 ` dpdklab
2024-04-05 14:49 ` dpdklab
2024-04-05 14:49 ` |WARNING| " dpdklab
2024-04-05 14:49 ` |SUCCESS| " dpdklab
2024-04-05 14:50 ` dpdklab
2024-04-05 14:50 ` dpdklab
2024-04-05 14:50 ` dpdklab
2024-04-05 14:51 ` dpdklab
2024-04-05 14:51 ` dpdklab
2024-04-05 14:51 ` dpdklab
2024-04-05 14:52 ` dpdklab
2024-04-05 14:52 ` dpdklab
2024-04-05 14:56 ` |WARNING| " dpdklab
2024-04-05 14:57 ` dpdklab
2024-04-05 14:57 ` |SUCCESS| " dpdklab
2024-04-05 14:57 ` |WARNING| " dpdklab
2024-04-05 14:58 ` dpdklab
2024-04-05 14:58 ` |SUCCESS| " dpdklab
2024-04-05 14:58 ` dpdklab
2024-04-05 14:58 ` dpdklab
2024-04-05 14:59 ` dpdklab
2024-04-05 14:59 ` dpdklab
2024-04-05 14:59 ` dpdklab
2024-04-05 15:00 ` dpdklab
2024-04-05 15:00 ` dpdklab
2024-04-05 15:00 ` |WARNING| " dpdklab
2024-04-05 15:00 ` |SUCCESS| " dpdklab
2024-04-05 15:00 ` dpdklab
2024-04-05 15:00 ` dpdklab
2024-04-05 15:01 ` dpdklab
2024-04-05 15:01 ` dpdklab
2024-04-05 15:02 ` dpdklab
2024-04-05 15:02 ` |WARNING| " dpdklab
2024-04-05 15:02 ` |SUCCESS| " dpdklab
2024-04-05 15:02 ` dpdklab
2024-04-05 15:02 ` dpdklab
2024-04-05 15:03 ` dpdklab
2024-04-05 15:03 ` dpdklab
2024-04-05 15:03 ` |WARNING| " dpdklab
2024-04-05 15:03 ` |SUCCESS| " dpdklab
2024-04-05 15:08 ` dpdklab
2024-04-05 15:21 ` dpdklab
2024-04-05 15:22 ` dpdklab
2024-04-05 15:23 ` dpdklab
2024-04-05 15:23 ` dpdklab
2024-04-05 15:24 ` dpdklab
2024-04-05 15:24 ` dpdklab
2024-04-05 15:24 ` dpdklab
2024-04-05 15:25 ` dpdklab
2024-04-05 15:26 ` |WARNING| " dpdklab
2024-04-05 15:26 ` dpdklab
2024-04-05 15:26 ` |SUCCESS| " dpdklab
2024-04-05 15:26 ` dpdklab
2024-04-05 15:27 ` |WARNING| " dpdklab
2024-04-05 15:28 ` |SUCCESS| " dpdklab
2024-04-05 15:30 ` dpdklab
2024-04-05 15:30 ` |WARNING| " dpdklab
2024-04-05 15:34 ` dpdklab
2024-04-05 15:35 ` dpdklab
2024-04-05 15:36 ` |SUCCESS| " dpdklab
2024-04-05 15:36 ` |WARNING| " dpdklab
2024-04-05 15:36 ` |SUCCESS| " dpdklab
2024-04-05 15:36 ` dpdklab
2024-04-05 15:38 ` dpdklab
2024-04-05 15:38 ` |WARNING| " dpdklab
2024-04-05 15:38 ` |SUCCESS| " dpdklab
2024-04-05 15:38 ` |WARNING| " dpdklab
2024-04-05 15:48 ` |SUCCESS| " dpdklab
2024-04-05 15:48 ` |WARNING| " dpdklab
2024-04-05 15:51 ` dpdklab
2024-04-05 15:52 ` |SUCCESS| " dpdklab
2024-04-05 15:53 ` |WARNING| " dpdklab
2024-04-05 16:04 ` |SUCCESS| " dpdklab
2024-04-05 16:08 ` dpdklab
2024-04-05 16:10 ` 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=20240405135005.38292121EEE@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).