From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138010 [PATCH] net/hns3: fix user priority 4-7 didn't enable PFC
Date: Wed, 6 Mar 2024 10:26:33 +0100 (CET) [thread overview]
Message-ID: <20240306092633.CCFB4122335@dpdk.org> (raw)
In-Reply-To: <20240306092047.492864-1-haijie1@huawei.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138010
_coding style OK_
next prev parent reply other threads:[~2024-03-06 9:26 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240306092047.492864-1-haijie1@huawei.com>
2024-03-06 9:08 ` qemudev
2024-03-06 9:12 ` qemudev
2024-03-06 9:26 ` checkpatch [this message]
2024-03-06 10:24 ` 0-day Robot
2024-03-06 12:39 ` |SUCCESS| pw138010 [PATCH] net/hns3: fix user priority 4-7 didn't en dpdklab
2024-03-06 12:40 ` dpdklab
2024-03-06 12:43 ` dpdklab
2024-03-06 12:45 ` dpdklab
2024-03-06 12:46 ` dpdklab
2024-03-06 12:47 ` dpdklab
2024-03-06 12:48 ` dpdklab
2024-03-06 12:50 ` dpdklab
2024-03-06 12:59 ` dpdklab
2024-03-06 13:00 ` dpdklab
2024-03-06 13:07 ` dpdklab
2024-03-06 13:09 ` dpdklab
2024-03-06 13:19 ` dpdklab
2024-03-06 13:19 ` dpdklab
2024-03-06 13:20 ` dpdklab
2024-03-06 13:22 ` dpdklab
2024-03-06 13:31 ` dpdklab
2024-03-06 13:31 ` dpdklab
2024-03-06 13:34 ` dpdklab
2024-03-06 13:34 ` dpdklab
2024-03-06 13:45 ` dpdklab
2024-03-06 14:31 ` dpdklab
2024-03-06 14:56 ` dpdklab
2024-03-06 15:06 ` dpdklab
2024-03-06 15:07 ` dpdklab
2024-03-06 15:07 ` dpdklab
2024-03-06 15:08 ` dpdklab
2024-03-06 15:08 ` dpdklab
2024-03-06 15:09 ` dpdklab
2024-03-06 15:09 ` dpdklab
2024-03-06 15:09 ` dpdklab
2024-03-06 15:11 ` dpdklab
2024-03-06 15:11 ` dpdklab
2024-03-06 15:12 ` dpdklab
2024-03-06 15:13 ` dpdklab
2024-03-06 15:13 ` dpdklab
2024-03-06 15:14 ` dpdklab
2024-03-06 15:15 ` dpdklab
2024-03-06 15:15 ` dpdklab
2024-03-06 15:15 ` dpdklab
2024-03-06 15:16 ` dpdklab
2024-03-06 15:21 ` dpdklab
2024-03-06 15:21 ` dpdklab
2024-03-06 15:22 ` dpdklab
2024-03-06 15:23 ` dpdklab
2024-03-06 15:23 ` dpdklab
2024-03-06 15:25 ` dpdklab
2024-03-06 15:25 ` dpdklab
2024-03-06 15:25 ` dpdklab
2024-03-06 15:26 ` dpdklab
2024-03-06 15:26 ` dpdklab
2024-03-06 15:27 ` dpdklab
2024-03-06 15:27 ` dpdklab
2024-03-06 15:34 ` dpdklab
2024-03-06 15:37 ` dpdklab
2024-03-06 15:46 ` dpdklab
2024-03-06 15:46 ` dpdklab
2024-03-06 15:47 ` dpdklab
2024-03-06 15:53 ` dpdklab
2024-03-06 16:10 ` dpdklab
2024-03-06 16:10 ` dpdklab
2024-03-06 16:11 ` dpdklab
2024-03-06 16:12 ` dpdklab
2024-03-06 16:20 ` dpdklab
2024-03-06 16:31 ` dpdklab
2024-03-06 18:25 ` dpdklab
2024-03-06 20:36 ` 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=20240306092633.CCFB4122335@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).