From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw137660 [PATCH v5] net/i40e: add diagnostic support in TX path
Date: Fri, 1 Mar 2024 11:04:13 +0100 (CET) [thread overview]
Message-ID: <20240301100413.54C6812232A@dpdk.org> (raw)
In-Reply-To: <20240301094422.460012-1-mingjinx.ye@intel.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/137660
_coding style OK_
next parent reply other threads:[~2024-03-01 10:04 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240301094422.460012-1-mingjinx.ye@intel.com>
2024-03-01 10:04 ` checkpatch [this message]
2024-03-01 11:05 ` 0-day Robot
2024-03-01 15:17 ` |SUCCESS| pw137660 [PATCH] [v5] net/i40e: add diagnostic support in dpdklab
2024-03-01 15:21 ` |FAILURE| " dpdklab
2024-03-01 15:48 ` |SUCCESS| " dpdklab
2024-03-01 15:58 ` |FAILURE| " dpdklab
2024-03-01 15:59 ` |SUCCESS| " dpdklab
2024-03-01 16:00 ` dpdklab
2024-03-01 16:09 ` dpdklab
2024-03-01 16:10 ` dpdklab
2024-03-01 16:11 ` dpdklab
2024-03-01 16:11 ` dpdklab
2024-03-01 16:14 ` dpdklab
2024-03-01 16:16 ` dpdklab
2024-03-01 16:28 ` dpdklab
2024-03-01 16:35 ` |FAILURE| " dpdklab
2024-03-01 16:38 ` |SUCCESS| " dpdklab
2024-03-01 16:43 ` dpdklab
2024-03-01 16:44 ` dpdklab
2024-03-01 16:45 ` dpdklab
2024-03-01 18:07 ` |FAILURE| " dpdklab
2024-03-01 18:17 ` |SUCCESS| " dpdklab
2024-03-01 18:27 ` dpdklab
2024-03-01 18:27 ` dpdklab
2024-03-01 18:28 ` dpdklab
2024-03-01 18:28 ` dpdklab
2024-03-01 18:30 ` dpdklab
2024-03-01 18:31 ` dpdklab
2024-03-01 18:32 ` dpdklab
2024-03-01 18:32 ` dpdklab
2024-03-01 18:36 ` dpdklab
2024-03-01 18:37 ` dpdklab
2024-03-01 18:37 ` dpdklab
2024-03-01 18:37 ` dpdklab
2024-03-01 18:37 ` dpdklab
2024-03-01 18:38 ` dpdklab
2024-03-01 18:38 ` dpdklab
2024-03-01 18:39 ` dpdklab
2024-03-01 18:39 ` dpdklab
2024-03-01 18:39 ` dpdklab
2024-03-01 18:40 ` dpdklab
2024-03-01 18:40 ` dpdklab
2024-03-01 18:40 ` dpdklab
2024-03-01 18:40 ` dpdklab
2024-03-01 18:41 ` dpdklab
2024-03-01 18:41 ` dpdklab
2024-03-01 18:41 ` dpdklab
2024-03-01 18:41 ` dpdklab
2024-03-01 18:42 ` dpdklab
2024-03-01 18:42 ` dpdklab
2024-03-01 18:42 ` dpdklab
2024-03-01 18:42 ` dpdklab
2024-03-01 18:42 ` dpdklab
2024-03-01 18:43 ` dpdklab
2024-03-01 18:43 ` dpdklab
2024-03-01 18:43 ` dpdklab
2024-03-01 18:43 ` dpdklab
2024-03-01 18:44 ` dpdklab
2024-03-01 18:46 ` dpdklab
2024-03-01 18:46 ` dpdklab
2024-03-01 18:46 ` dpdklab
2024-03-01 18:48 ` dpdklab
2024-03-01 18:57 ` dpdklab
2024-03-01 19:09 ` dpdklab
2024-03-01 19:15 ` dpdklab
2024-03-01 19:54 ` dpdklab
2024-03-01 19:58 ` dpdklab
2024-03-01 20:03 ` |FAILURE| " dpdklab
2024-03-01 20:09 ` |SUCCESS| " dpdklab
2024-03-01 21:54 ` dpdklab
2024-03-01 22:29 ` dpdklab
2024-03-02 1:56 ` dpdklab
2024-03-02 2:03 ` dpdklab
2024-03-02 6:33 ` |SUCCESS| pw137660 [PATCH v5] net/i40e: add diagnostic support in TX path qemudev
2024-03-02 6:37 ` qemudev
2024-03-02 20:11 ` |SUCCESS| pw137660 [PATCH] [v5] net/i40e: add diagnostic support in dpdklab
2024-03-05 9:45 ` dpdklab
2024-03-05 10:06 ` dpdklab
2024-03-05 10:30 ` 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=20240301100413.54C6812232A@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).