From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw142403 [PATCH v1] test/crypto: remove unused stats in test setup
Date: Mon, 15 Jul 2024 15:38:25 +0200 (CEST) [thread overview]
Message-ID: <20240715133825.E98D4127EE2@dpdk.org> (raw)
In-Reply-To: <20240715133613.1459-1-gmuthukrishn@marvell.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/142403
_coding style OK_
next prev parent reply other threads:[~2024-07-15 13:38 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240715133613.1459-1-gmuthukrishn@marvell.com>
2024-07-15 13:33 ` qemudev
2024-07-15 13:38 ` checkpatch [this message]
2024-07-15 13:38 ` qemudev
2024-07-15 14:23 ` 0-day Robot
2024-07-15 16:30 ` |PENDING| pw142403 [PATCH] [v1] test/crypto: remove unused stats in dpdklab
2024-07-15 16:33 ` dpdklab
2024-07-15 16:45 ` dpdklab
2024-07-15 16:48 ` dpdklab
2024-07-15 16:58 ` dpdklab
2024-07-15 17:04 ` dpdklab
2024-07-15 17:05 ` dpdklab
2024-07-15 17:07 ` dpdklab
2024-07-15 17:09 ` dpdklab
2024-07-15 17:09 ` dpdklab
2024-07-15 17:09 ` dpdklab
2024-07-15 17:10 ` dpdklab
2024-07-15 17:16 ` dpdklab
2024-07-15 17:24 ` dpdklab
2024-07-15 17:29 ` |SUCCESS| " dpdklab
2024-07-15 17:31 ` |PENDING| " dpdklab
2024-07-15 17:32 ` |SUCCESS| " dpdklab
2024-07-15 17:38 ` dpdklab
2024-07-15 17:46 ` dpdklab
2024-07-15 17:52 ` |PENDING| " dpdklab
2024-07-15 17:54 ` dpdklab
2024-07-15 17:57 ` |SUCCESS| " dpdklab
2024-07-15 17:57 ` dpdklab
2024-07-15 18:03 ` |PENDING| " dpdklab
2024-07-15 18:19 ` |SUCCESS| " dpdklab
2024-07-15 19:01 ` |PENDING| " dpdklab
2024-07-15 19:37 ` dpdklab
2024-07-15 19:49 ` dpdklab
2024-07-15 20:17 ` dpdklab
2024-07-15 20:24 ` |SUCCESS| " dpdklab
2024-07-15 20:33 ` dpdklab
2024-07-15 20:40 ` |PENDING| " dpdklab
2024-07-15 20:49 ` dpdklab
2024-07-15 20:50 ` dpdklab
2024-07-15 20:53 ` dpdklab
2024-07-15 20:58 ` dpdklab
2024-07-15 21:14 ` dpdklab
2024-07-15 21:20 ` dpdklab
2024-07-15 21:22 ` dpdklab
2024-07-15 21:23 ` dpdklab
2024-07-15 21:24 ` dpdklab
2024-07-15 21:27 ` dpdklab
2024-07-15 21:27 ` dpdklab
2024-07-15 21:31 ` dpdklab
2024-07-15 21:34 ` dpdklab
2024-07-15 21:37 ` dpdklab
2024-07-15 21:40 ` dpdklab
2024-07-15 21:45 ` dpdklab
2024-07-15 21:46 ` dpdklab
2024-07-15 21:51 ` dpdklab
2024-07-15 21:53 ` dpdklab
2024-07-15 21:54 ` dpdklab
2024-07-15 21:57 ` dpdklab
2024-07-15 22:02 ` dpdklab
2024-07-15 22:02 ` dpdklab
2024-07-15 22:04 ` dpdklab
2024-07-15 22:05 ` dpdklab
2024-07-15 22:08 ` dpdklab
2024-07-15 22:08 ` dpdklab
2024-07-15 22:10 ` dpdklab
2024-07-15 22:30 ` dpdklab
2024-07-15 22:36 ` dpdklab
2024-07-15 22:36 ` dpdklab
2024-07-15 22:37 ` dpdklab
2024-07-15 22:42 ` dpdklab
2024-07-15 22:42 ` dpdklab
2024-07-15 22:44 ` dpdklab
2024-07-15 22:48 ` dpdklab
2024-07-15 22:48 ` dpdklab
2024-07-15 22:51 ` dpdklab
2024-07-15 22:52 ` dpdklab
2024-07-15 22:52 ` dpdklab
2024-07-15 22:52 ` dpdklab
2024-07-15 22:54 ` dpdklab
2024-07-15 22:55 ` dpdklab
2024-07-15 22:56 ` dpdklab
2024-07-15 23:00 ` dpdklab
2024-07-15 23:01 ` dpdklab
2024-07-15 23:13 ` dpdklab
2024-07-15 23:20 ` dpdklab
2024-07-15 23:22 ` dpdklab
2024-07-15 23:27 ` dpdklab
2024-07-15 23:35 ` dpdklab
2024-07-15 23:51 ` |SUCCESS| " dpdklab
2024-07-16 0:02 ` |PENDING| " dpdklab
2024-07-16 0:06 ` dpdklab
2024-07-16 0:07 ` dpdklab
2024-07-16 0:11 ` dpdklab
2024-07-16 0:13 ` dpdklab
2024-07-16 0:19 ` dpdklab
2024-07-16 0:23 ` dpdklab
2024-07-16 0:23 ` dpdklab
2024-07-16 0:27 ` dpdklab
2024-07-16 0:29 ` dpdklab
2024-07-16 0:32 ` dpdklab
2024-07-16 0:34 ` dpdklab
2024-07-16 0:35 ` dpdklab
2024-07-16 0:35 ` dpdklab
2024-07-16 0:39 ` dpdklab
2024-07-16 0:42 ` |SUCCESS| " dpdklab
2024-07-16 0:43 ` dpdklab
2024-07-16 8:48 ` dpdklab
2024-07-16 12:34 ` dpdklab
2024-07-16 12:38 ` dpdklab
2024-07-16 13:07 ` dpdklab
2024-07-16 13:37 ` dpdklab
2024-07-16 13:58 ` 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=20240715133825.E98D4127EE2@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).