From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw141510 [PATCH 2/2] net/bonding: add command to set dedicated queue size
Date: Mon, 24 Jun 2024 04:05:05 +0200 (CEST) [thread overview]
Message-ID: <20240624020505.8C0A7128144@dpdk.org> (raw)
In-Reply-To: <20240624020355.3712965-3-chaoyong.he@corigine.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/141510
_coding style OK_
next prev parent reply other threads:[~2024-06-24 2:05 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240624020355.3712965-3-chaoyong.he@corigine.com>
2024-06-24 1:45 ` |SUCCESS| pw141509-141510 " qemudev
2024-06-24 1:50 ` qemudev
2024-06-24 2:05 ` checkpatch [this message]
2024-06-24 8:31 ` |SUCCESS| pw141509-141510 [PATCH] [2/2] net/bonding: add command to dpdklab
2024-06-24 8:45 ` dpdklab
2024-06-24 8:45 ` dpdklab
2024-06-24 8:56 ` dpdklab
2024-06-24 8:57 ` dpdklab
2024-06-24 9:07 ` dpdklab
2024-06-24 9:09 ` dpdklab
2024-06-24 9:11 ` dpdklab
2024-06-24 9:12 ` dpdklab
2024-06-24 9:12 ` dpdklab
2024-06-24 9:19 ` dpdklab
2024-06-24 9:19 ` dpdklab
2024-06-24 9:21 ` dpdklab
2024-06-24 9:24 ` dpdklab
2024-06-24 9:25 ` dpdklab
2024-06-24 9:25 ` dpdklab
2024-06-24 9:26 ` dpdklab
2024-06-24 9:27 ` dpdklab
2024-06-24 9:28 ` dpdklab
2024-06-24 9:35 ` dpdklab
2024-06-24 9:35 ` dpdklab
2024-06-24 9:36 ` dpdklab
2024-06-24 9:36 ` dpdklab
2024-06-24 9:37 ` dpdklab
2024-06-24 9:37 ` dpdklab
2024-06-24 9:38 ` dpdklab
2024-06-24 9:38 ` dpdklab
2024-06-24 9:39 ` dpdklab
2024-06-24 9:40 ` dpdklab
2024-06-24 9:40 ` dpdklab
2024-06-24 9:51 ` dpdklab
2024-06-24 9:51 ` dpdklab
2024-06-24 10:05 ` dpdklab
2024-06-24 10:15 ` dpdklab
2024-06-24 10:15 ` dpdklab
2024-06-24 10:16 ` dpdklab
2024-06-24 10:16 ` dpdklab
2024-06-24 10:17 ` dpdklab
2024-06-24 10:17 ` dpdklab
2024-06-24 10:18 ` dpdklab
2024-06-24 10:20 ` dpdklab
2024-06-24 10:28 ` dpdklab
2024-06-24 10:29 ` dpdklab
2024-06-24 10:30 ` dpdklab
2024-06-24 10:31 ` dpdklab
2024-06-24 10:31 ` dpdklab
2024-06-24 10:34 ` dpdklab
2024-06-24 10:37 ` dpdklab
2024-06-24 10:38 ` dpdklab
2024-06-24 10:39 ` dpdklab
2024-06-24 10:41 ` dpdklab
2024-06-24 10:42 ` dpdklab
2024-06-24 10:45 ` dpdklab
2024-06-24 10:46 ` dpdklab
2024-06-24 10:47 ` dpdklab
2024-06-24 10:48 ` dpdklab
2024-06-24 10:49 ` dpdklab
2024-06-24 10:50 ` dpdklab
2024-06-24 10:51 ` dpdklab
2024-06-24 10:52 ` dpdklab
2024-06-24 10:52 ` dpdklab
2024-06-24 10:52 ` dpdklab
2024-06-24 10:53 ` dpdklab
2024-06-24 10:53 ` dpdklab
2024-06-24 10:55 ` dpdklab
2024-06-24 10:56 ` dpdklab
2024-06-24 10:56 ` dpdklab
2024-06-24 10:57 ` dpdklab
2024-06-24 10:57 ` dpdklab
2024-06-24 10:58 ` dpdklab
2024-06-24 11:03 ` dpdklab
2024-06-24 11:26 ` dpdklab
2024-06-24 11:27 ` dpdklab
2024-06-24 11:30 ` dpdklab
2024-06-24 11:30 ` dpdklab
2024-06-24 11:30 ` dpdklab
2024-06-24 11:31 ` dpdklab
2024-06-24 11:31 ` dpdklab
2024-06-24 11:31 ` dpdklab
2024-06-24 11:32 ` dpdklab
2024-06-24 11:33 ` dpdklab
2024-06-24 11:33 ` dpdklab
2024-06-24 11:33 ` dpdklab
2024-06-24 11:34 ` dpdklab
2024-06-24 11:35 ` dpdklab
2024-06-24 11:35 ` dpdklab
2024-06-24 11:35 ` dpdklab
2024-06-24 11:36 ` dpdklab
2024-06-24 11:37 ` dpdklab
2024-06-24 11:38 ` dpdklab
2024-06-24 11:38 ` dpdklab
2024-06-24 11:39 ` dpdklab
2024-06-24 11:40 ` dpdklab
2024-06-24 11:40 ` dpdklab
2024-06-24 11:40 ` dpdklab
2024-06-24 11:40 ` dpdklab
2024-06-24 11:41 ` dpdklab
2024-06-24 11:41 ` dpdklab
2024-06-24 11:41 ` dpdklab
2024-06-24 11:42 ` dpdklab
2024-06-24 11:58 ` dpdklab
2024-06-24 11:59 ` dpdklab
2024-06-24 12:01 ` dpdklab
2024-06-24 12:26 ` dpdklab
2024-06-24 12:27 ` dpdklab
2024-06-24 12:27 ` dpdklab
2024-06-24 12:28 ` dpdklab
2024-06-24 12:29 ` dpdklab
2024-06-24 12:29 ` dpdklab
2024-06-24 12:30 ` dpdklab
2024-06-24 12:32 ` dpdklab
2024-06-24 12:37 ` dpdklab
2024-06-24 13:12 ` dpdklab
2024-06-24 13:51 ` 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=20240624020505.8C0A7128144@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).