From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw146210-146213 [PATCH 4/4] net/hns3: support outer VLAN flow match
Date: Fri, 18 Oct 2024 14:05:14 +0800 [thread overview]
Message-ID: <202410180605.49I65EuL3300294@localhost.localdomain> (raw)
In-Reply-To: <20241018061941.29960-5-haijie1@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/146213
_Compilation OK_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Fri, 18 Oct 2024 14:19:38 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 03d37ac13b61563fb31e4a0f5d0e427a61d548d5
146210-146213 --> meson & ninja build successfully
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
next parent reply other threads:[~2024-10-18 6:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241018061941.29960-5-haijie1@huawei.com>
2024-10-18 6:05 ` qemudev [this message]
2024-10-18 6:09 ` qemudev
2024-10-18 6:33 ` |WARNING| pw146213 " checkpatch
2024-10-18 7:22 ` |SUCCESS| " 0-day Robot
2024-10-18 12:57 ` |SUCCESS| pw146210-146213 [PATCH] [4/4] net/hns3: support outer VLAN dpdklab
2024-10-19 0:45 ` dpdklab
2024-10-19 1:28 ` dpdklab
2024-10-19 2:08 ` dpdklab
2024-10-19 6:27 ` |PENDING| " dpdklab
2024-10-19 6:34 ` |SUCCESS| " dpdklab
2024-10-19 6:44 ` |PENDING| " dpdklab
2024-10-19 6:57 ` |FAILURE| " dpdklab
2024-10-19 7:33 ` dpdklab
2024-10-19 7:33 ` dpdklab
2024-10-19 7:36 ` dpdklab
2024-10-19 10:07 ` |SUCCESS| " dpdklab
2024-10-19 10:34 ` |FAILURE| " dpdklab
2024-10-19 11:31 ` |SUCCESS| " dpdklab
2024-10-19 11:34 ` dpdklab
2024-10-19 12:34 ` dpdklab
2024-10-22 4:06 ` dpdklab
2024-10-23 8:39 ` dpdklab
2024-10-23 8:42 ` dpdklab
2024-10-26 7:48 ` |FAILURE| " dpdklab
2024-10-28 9:12 ` |PENDING| " dpdklab
2024-11-01 20:26 ` |SUCCESS| " 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=202410180605.49I65EuL3300294@localhost.localdomain \
--to=qemudev@loongson.cn \
--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).