From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138011 [PATCH] net/hns3: support new device
Date: Wed, 6 Mar 2024 10:26:31 +0100 (CET) [thread overview]
Message-ID: <20240306092631.910EE122335@dpdk.org> (raw)
In-Reply-To: <20240306092112.506493-1-haijie1@huawei.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138011
_coding style OK_
next prev parent reply other threads:[~2024-03-06 9:26 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240306092112.506493-1-haijie1@huawei.com>
2024-03-06 9:02 ` qemudev
2024-03-06 9:06 ` qemudev
2024-03-06 9:26 ` checkpatch [this message]
2024-03-06 10:24 ` 0-day Robot
2024-03-06 12:20 ` dpdklab
2024-03-06 12:21 ` dpdklab
2024-03-06 12:22 ` dpdklab
2024-03-06 12:22 ` dpdklab
2024-03-06 12:30 ` dpdklab
2024-03-06 12:30 ` dpdklab
2024-03-06 12:30 ` dpdklab
2024-03-06 12:37 ` dpdklab
2024-03-06 12:38 ` dpdklab
2024-03-06 12:38 ` dpdklab
2024-03-06 12:43 ` dpdklab
2024-03-06 12:49 ` dpdklab
2024-03-06 12:51 ` dpdklab
2024-03-06 12:51 ` dpdklab
2024-03-06 12:51 ` dpdklab
2024-03-06 13:16 ` dpdklab
2024-03-06 13:17 ` dpdklab
2024-03-06 13:17 ` dpdklab
2024-03-06 13:18 ` dpdklab
2024-03-06 13:18 ` dpdklab
2024-03-06 13:19 ` dpdklab
2024-03-06 14:01 ` dpdklab
2024-03-06 14:03 ` dpdklab
2024-03-06 14:05 ` dpdklab
2024-03-06 14:10 ` dpdklab
2024-03-06 14:11 ` dpdklab
2024-03-06 14:11 ` dpdklab
2024-03-06 14:13 ` dpdklab
2024-03-06 14:13 ` dpdklab
2024-03-06 14:14 ` dpdklab
2024-03-06 14:15 ` dpdklab
2024-03-06 14:15 ` dpdklab
2024-03-06 14:25 ` dpdklab
2024-03-06 14:26 ` dpdklab
2024-03-06 14:27 ` dpdklab
2024-03-06 14:38 ` dpdklab
2024-03-06 14:49 ` dpdklab
2024-03-06 14:50 ` dpdklab
2024-03-06 14:51 ` dpdklab
2024-03-06 14:52 ` dpdklab
2024-03-06 14:53 ` dpdklab
2024-03-06 14:53 ` dpdklab
2024-03-06 14:54 ` dpdklab
2024-03-06 14:54 ` dpdklab
2024-03-06 14:55 ` dpdklab
2024-03-06 15:05 ` dpdklab
2024-03-06 15:06 ` dpdklab
2024-03-06 15:06 ` dpdklab
2024-03-06 15:07 ` dpdklab
2024-03-06 15:10 ` dpdklab
2024-03-06 15:10 ` dpdklab
2024-03-06 15:10 ` dpdklab
2024-03-06 15:12 ` dpdklab
2024-03-06 15:12 ` dpdklab
2024-03-06 15:12 ` dpdklab
2024-03-06 15:14 ` dpdklab
2024-03-06 15:15 ` dpdklab
2024-03-06 15:16 ` dpdklab
2024-03-06 15:17 ` dpdklab
2024-03-06 15:18 ` dpdklab
2024-03-06 15:22 ` dpdklab
2024-03-06 15:23 ` dpdklab
2024-03-06 15:26 ` dpdklab
2024-03-06 15:34 ` dpdklab
2024-03-06 15:36 ` dpdklab
2024-03-06 15:44 ` dpdklab
2024-03-06 16:21 ` dpdklab
2024-03-06 16:25 ` dpdklab
2024-03-06 17:29 ` dpdklab
2024-03-06 19:46 ` 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=20240306092631.910EE122335@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).