From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw142867 [PATCH] netvsc: optimize stats counters performance
Date: Fri, 2 Aug 2024 16:42:08 +0200 (CEST) [thread overview]
Message-ID: <20240802144208.4C685123EF2@dpdk.org> (raw)
In-Reply-To: <20240802144048.270152-1-mb@smartsharesystems.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/142867
_coding style OK_
next prev parent reply other threads:[~2024-08-02 14:42 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240802144048.270152-1-mb@smartsharesystems.com>
2024-08-02 14:14 ` qemudev
2024-08-02 14:18 ` qemudev
2024-08-02 14:42 ` checkpatch [this message]
2024-08-02 15:42 ` 0-day Robot
2024-08-02 18:09 ` |SUCCESS| pw142867 [PATCH] netvsc: optimize stats counters performan dpdklab
2024-08-02 18:11 ` |PENDING| " dpdklab
2024-08-02 18:13 ` dpdklab
2024-08-02 18:15 ` |SUCCESS| " dpdklab
2024-08-02 18:23 ` dpdklab
2024-08-02 18:24 ` dpdklab
2024-08-02 18:25 ` |PENDING| " dpdklab
2024-08-02 18:25 ` |SUCCESS| " dpdklab
2024-08-02 18:26 ` dpdklab
2024-08-02 18:27 ` |PENDING| " dpdklab
2024-08-02 18:28 ` dpdklab
2024-08-02 18:28 ` |SUCCESS| " dpdklab
2024-08-02 18:30 ` dpdklab
2024-08-02 18:31 ` |PENDING| " dpdklab
2024-08-02 18:31 ` dpdklab
2024-08-02 18:31 ` dpdklab
2024-08-02 18:32 ` dpdklab
2024-08-02 18:32 ` dpdklab
2024-08-02 18:32 ` dpdklab
2024-08-02 18:35 ` |SUCCESS| " dpdklab
2024-08-02 18:36 ` |PENDING| " dpdklab
2024-08-02 18:36 ` dpdklab
2024-08-02 18:38 ` dpdklab
2024-08-02 18:39 ` dpdklab
2024-08-02 18:39 ` |SUCCESS| " dpdklab
2024-08-02 18:40 ` |PENDING| " dpdklab
2024-08-02 18:40 ` dpdklab
2024-08-02 18:42 ` dpdklab
2024-08-02 18:43 ` dpdklab
2024-08-02 18:43 ` dpdklab
2024-08-02 18:44 ` dpdklab
2024-08-02 18:45 ` dpdklab
2024-08-02 18:46 ` dpdklab
2024-08-02 18:47 ` dpdklab
2024-08-02 18:47 ` dpdklab
2024-08-02 18:48 ` dpdklab
2024-08-02 18:48 ` dpdklab
2024-08-02 18:49 ` dpdklab
2024-08-02 18:50 ` dpdklab
2024-08-02 18:50 ` dpdklab
2024-08-02 18:50 ` dpdklab
2024-08-02 18:51 ` dpdklab
2024-08-02 18:53 ` dpdklab
2024-08-02 18:54 ` dpdklab
2024-08-02 18:54 ` dpdklab
2024-08-02 18:54 ` dpdklab
2024-08-02 18:57 ` dpdklab
2024-08-02 18:58 ` dpdklab
2024-08-02 18:59 ` |SUCCESS| " dpdklab
2024-08-02 18:59 ` dpdklab
2024-08-02 18:59 ` |PENDING| " dpdklab
2024-08-02 19:00 ` dpdklab
2024-08-02 19:00 ` dpdklab
2024-08-02 19:00 ` dpdklab
2024-08-02 19:02 ` dpdklab
2024-08-02 19:04 ` dpdklab
2024-08-02 19:05 ` dpdklab
2024-08-02 19:07 ` dpdklab
2024-08-02 19:08 ` dpdklab
2024-08-02 19:08 ` dpdklab
2024-08-02 19:08 ` dpdklab
2024-08-02 19:09 ` dpdklab
2024-08-02 19:10 ` dpdklab
2024-08-02 19:13 ` dpdklab
2024-08-02 19:13 ` dpdklab
2024-08-02 19:14 ` dpdklab
2024-08-02 19:15 ` dpdklab
2024-08-02 19:16 ` |SUCCESS| " dpdklab
2024-08-02 19:17 ` dpdklab
2024-08-02 19:17 ` |PENDING| " dpdklab
2024-08-02 19:17 ` dpdklab
2024-08-02 19:17 ` dpdklab
2024-08-02 19:19 ` dpdklab
2024-08-02 19:20 ` dpdklab
2024-08-02 19:21 ` dpdklab
2024-08-02 19:22 ` dpdklab
2024-08-02 19:22 ` dpdklab
2024-08-02 19:22 ` dpdklab
2024-08-02 19:23 ` dpdklab
2024-08-02 19:23 ` dpdklab
2024-08-02 19:25 ` dpdklab
2024-08-02 19:25 ` dpdklab
2024-08-02 19:26 ` dpdklab
2024-08-02 19:27 ` |SUCCESS| " dpdklab
2024-08-02 19:27 ` |PENDING| " dpdklab
2024-08-02 19:27 ` dpdklab
2024-08-02 19:27 ` |SUCCESS| " dpdklab
2024-08-02 19:31 ` |PENDING| " dpdklab
2024-08-02 19:32 ` dpdklab
2024-08-02 19:32 ` dpdklab
2024-08-02 19:33 ` dpdklab
2024-08-02 19:38 ` dpdklab
2024-08-02 19:39 ` dpdklab
2024-08-02 19:40 ` dpdklab
2024-08-02 19:43 ` dpdklab
2024-08-02 19:44 ` dpdklab
2024-08-02 19:45 ` dpdklab
2024-08-02 19:48 ` dpdklab
2024-08-02 19:48 ` dpdklab
2024-08-02 19:50 ` |SUCCESS| " dpdklab
2024-08-02 19:52 ` |PENDING| " dpdklab
2024-08-02 20:02 ` dpdklab
2024-08-02 20:03 ` |SUCCESS| " dpdklab
2024-08-02 20:07 ` dpdklab
2024-08-03 10:08 ` dpdklab
2024-08-06 13:07 ` dpdklab
2024-08-06 13:16 ` 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=20240802144208.4C685123EF2@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).