From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138135 [PATCH v3] app/dma-perf: add average latency per worker
Date: Fri, 8 Mar 2024 20:08:49 +0100 (CET) [thread overview]
Message-ID: <20240308190849.77AB01223EF@dpdk.org> (raw)
In-Reply-To: <20240308190646.1456-1-vipin.varghese@amd.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138135
_coding style OK_
next prev parent reply other threads:[~2024-03-08 19:08 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240308190646.1456-1-vipin.varghese@amd.com>
2024-03-08 18:43 ` qemudev
2024-03-08 18:47 ` qemudev
2024-03-08 19:08 ` checkpatch [this message]
2024-03-08 20:07 ` 0-day Robot
2024-03-08 22:07 ` |SUCCESS| pw138135 [PATCH] [v3] app/dma-perf: add average latency pe dpdklab
2024-03-08 22:10 ` dpdklab
2024-03-08 22:18 ` dpdklab
2024-03-08 22:19 ` dpdklab
2024-03-08 22:20 ` dpdklab
2024-03-08 22:26 ` dpdklab
2024-03-08 22:26 ` dpdklab
2024-03-08 22:30 ` dpdklab
2024-03-08 22:31 ` dpdklab
2024-03-08 22:41 ` dpdklab
2024-03-08 22:43 ` dpdklab
2024-03-08 22:53 ` dpdklab
2024-03-08 22:58 ` dpdklab
2024-03-08 23:00 ` dpdklab
2024-03-08 23:00 ` dpdklab
2024-03-08 23:00 ` dpdklab
2024-03-08 23:01 ` dpdklab
2024-03-08 23:02 ` dpdklab
2024-03-08 23:03 ` dpdklab
2024-03-08 23:03 ` dpdklab
2024-03-08 23:04 ` dpdklab
2024-03-08 23:04 ` dpdklab
2024-03-08 23:04 ` dpdklab
2024-03-08 23:05 ` dpdklab
2024-03-08 23:06 ` dpdklab
2024-03-08 23:06 ` dpdklab
2024-03-08 23:07 ` dpdklab
2024-03-08 23:22 ` dpdklab
2024-03-08 23:24 ` dpdklab
2024-03-08 23:24 ` dpdklab
2024-03-08 23:24 ` dpdklab
2024-03-08 23:25 ` dpdklab
2024-03-08 23:25 ` dpdklab
2024-03-08 23:26 ` dpdklab
2024-03-08 23:26 ` dpdklab
2024-03-08 23:26 ` dpdklab
2024-03-08 23:27 ` dpdklab
2024-03-08 23:28 ` dpdklab
2024-03-08 23:28 ` dpdklab
2024-03-08 23:28 ` dpdklab
2024-03-08 23:28 ` dpdklab
2024-03-08 23:29 ` dpdklab
2024-03-08 23:29 ` dpdklab
2024-03-08 23:30 ` dpdklab
2024-03-08 23:30 ` dpdklab
2024-03-08 23:31 ` dpdklab
2024-03-08 23:34 ` dpdklab
2024-03-08 23:35 ` dpdklab
2024-03-08 23:35 ` dpdklab
2024-03-08 23:35 ` dpdklab
2024-03-08 23:35 ` dpdklab
2024-03-08 23:35 ` dpdklab
2024-03-08 23:36 ` dpdklab
2024-03-08 23:36 ` dpdklab
2024-03-08 23:36 ` dpdklab
2024-03-08 23:36 ` dpdklab
2024-03-08 23:55 ` dpdklab
2024-03-08 23:56 ` dpdklab
2024-03-08 23:57 ` dpdklab
2024-03-08 23:59 ` dpdklab
2024-03-09 0:00 ` dpdklab
2024-03-09 0:00 ` dpdklab
2024-03-09 0:04 ` dpdklab
2024-03-09 0:04 ` dpdklab
2024-03-09 0:04 ` dpdklab
2024-03-09 0:04 ` dpdklab
2024-03-09 0:04 ` dpdklab
2024-03-09 0:05 ` dpdklab
2024-03-09 0:49 ` dpdklab
2024-03-09 0:54 ` dpdklab
2024-03-13 14:13 ` dpdklab
2024-03-13 14:49 ` 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=20240308190849.77AB01223EF@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).