From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw141300 [PATCH 5/5] net/nfp: support getting Tx queue information
Date: Wed, 19 Jun 2024 04:50:43 +0200 (CEST) [thread overview]
Message-ID: <20240619025043.3963E12231F@dpdk.org> (raw)
In-Reply-To: <20240619024923.3215843-6-chaoyong.he@corigine.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/141300
_coding style OK_
next prev parent reply other threads:[~2024-06-19 2:50 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240619024923.3215843-6-chaoyong.he@corigine.com>
2024-06-19 2:27 ` |SUCCESS| pw141296-141300 " qemudev
2024-06-19 2:32 ` qemudev
2024-06-19 2:50 ` checkpatch [this message]
2024-06-19 3:44 ` |SUCCESS| pw141300 " 0-day Robot
2024-06-19 8:24 ` |SUCCESS| pw141296-141300 [PATCH] [5/5] net/nfp: support getting Tx dpdklab
2024-06-19 8:27 ` dpdklab
2024-06-19 8:27 ` dpdklab
2024-06-19 8:32 ` dpdklab
2024-06-19 8:34 ` dpdklab
2024-06-19 9:06 ` dpdklab
2024-06-19 9:06 ` dpdklab
2024-06-19 9:07 ` dpdklab
2024-06-19 9:12 ` dpdklab
2024-06-19 9:13 ` dpdklab
2024-06-19 9:13 ` dpdklab
2024-06-19 9:14 ` dpdklab
2024-06-19 9:14 ` dpdklab
2024-06-19 9:16 ` dpdklab
2024-06-19 9:37 ` dpdklab
2024-06-19 9:53 ` dpdklab
2024-06-19 10:26 ` dpdklab
2024-06-19 10:27 ` dpdklab
2024-06-19 10:28 ` dpdklab
2024-06-19 10:29 ` dpdklab
2024-06-19 10:29 ` dpdklab
2024-06-19 10:30 ` dpdklab
2024-06-19 10:31 ` dpdklab
2024-06-19 10:31 ` dpdklab
2024-06-19 10:32 ` dpdklab
2024-06-19 10:32 ` dpdklab
2024-06-19 10:34 ` dpdklab
2024-06-19 10:41 ` dpdklab
2024-06-19 10:42 ` dpdklab
2024-06-19 10:47 ` dpdklab
2024-06-19 11:46 ` dpdklab
2024-06-19 11:48 ` dpdklab
2024-06-19 11:49 ` dpdklab
2024-06-19 11:49 ` dpdklab
2024-06-19 11:51 ` dpdklab
2024-06-19 11:51 ` dpdklab
2024-06-19 11:52 ` dpdklab
2024-06-19 12:24 ` dpdklab
2024-06-19 14:20 ` dpdklab
2024-06-19 14:20 ` dpdklab
2024-06-19 14:22 ` dpdklab
2024-06-19 14:29 ` dpdklab
2024-06-19 14:30 ` dpdklab
2024-06-19 14:34 ` dpdklab
2024-06-19 14:36 ` dpdklab
2024-06-19 14:49 ` dpdklab
2024-06-19 14:53 ` dpdklab
2024-06-19 14:56 ` dpdklab
2024-06-19 15:04 ` dpdklab
2024-06-19 15:28 ` dpdklab
2024-06-19 15:31 ` dpdklab
2024-06-19 15:33 ` dpdklab
2024-06-19 15:34 ` dpdklab
2024-06-19 15:34 ` dpdklab
2024-06-19 16:10 ` dpdklab
2024-06-19 16:33 ` dpdklab
2024-06-19 16:41 ` dpdklab
2024-06-19 16:42 ` dpdklab
2024-06-19 16:43 ` dpdklab
2024-06-19 16:45 ` dpdklab
2024-06-19 16:53 ` dpdklab
2024-06-19 16:54 ` dpdklab
2024-06-19 16:56 ` dpdklab
2024-06-19 16:57 ` dpdklab
2024-06-19 17:00 ` dpdklab
2024-06-19 17:00 ` dpdklab
2024-06-19 17:05 ` dpdklab
2024-06-19 17:08 ` dpdklab
2024-06-19 17:09 ` dpdklab
2024-06-19 17:12 ` dpdklab
2024-06-19 17:13 ` dpdklab
2024-06-19 17:13 ` dpdklab
2024-06-19 17:13 ` dpdklab
2024-06-19 17:14 ` dpdklab
2024-06-19 17:15 ` dpdklab
2024-06-19 17:16 ` dpdklab
2024-06-19 17:18 ` dpdklab
2024-06-19 17:18 ` dpdklab
2024-06-19 17:18 ` dpdklab
2024-06-19 17:19 ` dpdklab
2024-06-19 17:23 ` dpdklab
2024-06-19 17:24 ` dpdklab
2024-06-19 17:24 ` dpdklab
2024-06-19 17:25 ` dpdklab
2024-06-19 17:25 ` dpdklab
2024-06-19 17:25 ` dpdklab
2024-06-19 17:27 ` dpdklab
2024-06-19 17:28 ` dpdklab
2024-06-19 17:30 ` dpdklab
2024-06-19 17:30 ` dpdklab
2024-06-19 17:32 ` dpdklab
2024-06-19 17:32 ` dpdklab
2024-06-19 17:33 ` dpdklab
2024-06-19 17:34 ` dpdklab
2024-06-19 17:34 ` dpdklab
2024-06-19 17:35 ` dpdklab
2024-06-19 17:35 ` dpdklab
2024-06-19 17:36 ` dpdklab
2024-06-19 17:36 ` dpdklab
2024-06-19 17:40 ` dpdklab
2024-06-19 17:44 ` dpdklab
2024-06-19 17:46 ` dpdklab
2024-06-19 17:47 ` dpdklab
2024-06-19 17:48 ` dpdklab
2024-06-19 17:56 ` dpdklab
2024-06-19 18:14 ` dpdklab
2024-06-19 18:20 ` dpdklab
2024-06-19 18:40 ` dpdklab
2024-06-19 18:51 ` dpdklab
2024-06-19 21:54 ` dpdklab
2024-06-19 22:11 ` dpdklab
2024-06-21 16:32 ` 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=20240619025043.3963E12231F@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).