From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw142118 [PATCH] net/hns3: support more VLAN fields matching
Date: Thu, 4 Jul 2024 04:16:18 +0200 (CEST) [thread overview]
Message-ID: <20240704021618.A4F52128144@dpdk.org> (raw)
In-Reply-To: <20240704021538.836403-1-haijie1@huawei.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/142118
_coding style OK_
next prev parent reply other threads:[~2024-07-04 2:16 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240704021538.836403-1-haijie1@huawei.com>
2024-07-04 1:49 ` qemudev
2024-07-04 1:53 ` qemudev
2024-07-04 2:16 ` checkpatch [this message]
2024-07-04 3:04 ` |FAILURE| " 0-day Robot
2024-07-04 10:58 ` |PENDING| pw142118 [PATCH] net/hns3: support more VLAN fields matchi dpdklab
2024-07-04 11:00 ` |SUCCESS| " dpdklab
2024-07-04 11:04 ` dpdklab
2024-07-04 11:08 ` dpdklab
2024-07-04 11:09 ` dpdklab
2024-07-04 11:11 ` dpdklab
2024-07-04 11:22 ` dpdklab
2024-07-04 12:24 ` dpdklab
2024-07-04 14:12 ` |PENDING| " dpdklab
2024-07-04 14:28 ` dpdklab
2024-07-04 14:28 ` dpdklab
2024-07-04 14:34 ` dpdklab
2024-07-04 14:36 ` dpdklab
2024-07-04 14:38 ` dpdklab
2024-07-04 14:42 ` dpdklab
2024-07-04 14:46 ` dpdklab
2024-07-04 14:48 ` dpdklab
2024-07-04 14:49 ` dpdklab
2024-07-04 14:53 ` dpdklab
2024-07-04 14:55 ` dpdklab
2024-07-04 14:56 ` dpdklab
2024-07-04 14:56 ` dpdklab
2024-07-04 14:57 ` dpdklab
2024-07-04 15:09 ` |SUCCESS| " dpdklab
2024-07-04 19:44 ` |PENDING| " dpdklab
2024-07-04 19:52 ` |SUCCESS| " dpdklab
2024-07-04 20:26 ` dpdklab
2024-07-04 22:59 ` dpdklab
2024-07-04 23:04 ` dpdklab
2024-07-04 23:09 ` dpdklab
2024-07-04 23:14 ` dpdklab
2024-07-04 23:34 ` dpdklab
2024-07-05 0:55 ` |PENDING| " dpdklab
2024-07-05 1:00 ` dpdklab
2024-07-05 1:12 ` |SUCCESS| " dpdklab
2024-07-05 1:19 ` |PENDING| " dpdklab
2024-07-05 1:53 ` dpdklab
2024-07-05 1:54 ` |SUCCESS| " dpdklab
2024-07-05 2:02 ` |PENDING| " dpdklab
2024-07-05 2:46 ` dpdklab
2024-07-05 4:33 ` dpdklab
2024-07-05 6:05 ` dpdklab
2024-07-05 9:50 ` dpdklab
2024-07-05 9:55 ` dpdklab
2024-07-05 9:59 ` dpdklab
2024-07-05 10:03 ` dpdklab
2024-07-05 10:03 ` dpdklab
2024-07-05 10:12 ` dpdklab
2024-07-05 10:12 ` dpdklab
2024-07-05 10:17 ` dpdklab
2024-07-05 10:19 ` dpdklab
2024-07-05 10:21 ` dpdklab
2024-07-05 10:21 ` dpdklab
2024-07-05 10:25 ` dpdklab
2024-07-05 10:28 ` |SUCCESS| " dpdklab
2024-07-05 12:04 ` |PENDING| " dpdklab
2024-07-05 12:04 ` dpdklab
2024-07-05 12:05 ` dpdklab
2024-07-05 12:07 ` dpdklab
2024-07-05 12:10 ` dpdklab
2024-07-05 12:13 ` dpdklab
2024-07-05 12:13 ` dpdklab
2024-07-05 12:18 ` dpdklab
2024-07-05 12:22 ` dpdklab
2024-07-05 12:29 ` dpdklab
2024-07-05 12:29 ` dpdklab
2024-07-05 12:31 ` dpdklab
2024-07-05 12:34 ` dpdklab
2024-07-05 12:35 ` dpdklab
2024-07-05 12:38 ` dpdklab
2024-07-05 12:43 ` dpdklab
2024-07-05 12:44 ` dpdklab
2024-07-05 12:50 ` |SUCCESS| " dpdklab
2024-07-05 12:59 ` |PENDING| " dpdklab
2024-07-05 13:06 ` dpdklab
2024-07-05 13:35 ` dpdklab
2024-07-05 13:36 ` dpdklab
2024-07-05 13:40 ` dpdklab
2024-07-05 13:43 ` dpdklab
2024-07-05 13:46 ` dpdklab
2024-07-05 13:48 ` dpdklab
2024-07-05 13:56 ` dpdklab
2024-07-05 14:05 ` dpdklab
2024-07-05 14:14 ` dpdklab
2024-07-05 14:16 ` dpdklab
2024-07-05 14:17 ` dpdklab
2024-07-05 14:19 ` dpdklab
2024-07-05 14:22 ` dpdklab
2024-07-05 14:23 ` dpdklab
2024-07-05 14:24 ` dpdklab
2024-07-05 14:30 ` dpdklab
2024-07-05 14:35 ` dpdklab
2024-07-05 14:36 ` dpdklab
2024-07-05 14:43 ` dpdklab
2024-07-05 14:48 ` dpdklab
2024-07-05 14:51 ` dpdklab
2024-07-05 14:57 ` dpdklab
2024-07-05 14:58 ` |SUCCESS| " dpdklab
2024-07-05 15:12 ` |PENDING| " dpdklab
2024-07-05 15:16 ` dpdklab
2024-07-05 15:18 ` dpdklab
2024-07-05 15:21 ` dpdklab
2024-07-05 15:24 ` dpdklab
2024-07-05 15:26 ` dpdklab
2024-07-05 15:51 ` dpdklab
2024-07-05 15:52 ` |SUCCESS| " dpdklab
2024-07-05 15:54 ` dpdklab
2024-07-05 19:26 ` dpdklab
2024-07-06 10:48 ` dpdklab
2024-07-06 12:20 ` dpdklab
2024-07-06 12:49 ` 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=20240704021618.A4F52128144@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).