From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138307 [PATCH v3 1/1] net/mana: add vlan tagging support
Date: Wed, 13 Mar 2024 17:44:30 +0800 [thread overview]
Message-ID: <202403130944.42D9iUHw4181943@localhost.localdomain> (raw)
In-Reply-To: <20240313090341.373037-1-weh@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138307
_Compilation OK_
Submitter: Wei Hu <weh@linux.microsoft.com>
Date: Wed, 13 Mar 2024 09:03:40 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 544d6d79a6ff0964a79a57efb102e87fdbd107d9
138307 --> 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-03-13 10:09 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240313090341.373037-1-weh@linux.microsoft.com>
2024-03-13 9:44 ` qemudev [this message]
2024-03-13 9:48 ` qemudev
2024-03-13 10:07 ` |WARNING| " checkpatch
2024-03-13 11:24 ` |SUCCESS| " 0-day Robot
2024-03-13 12:03 ` |SUCCESS| pw138307 [PATCH] [v3,1/1] net/mana: add vlan tagging suppo dpdklab
2024-03-13 12:05 ` dpdklab
2024-03-13 12:20 ` |FAILURE| " dpdklab
2024-03-13 12:20 ` |SUCCESS| " dpdklab
2024-03-13 12:21 ` dpdklab
2024-03-13 12:21 ` dpdklab
2024-03-13 12:22 ` dpdklab
2024-03-13 12:22 ` dpdklab
2024-03-13 12:23 ` dpdklab
2024-03-13 12:23 ` dpdklab
2024-03-13 12:23 ` dpdklab
2024-03-13 12:24 ` dpdklab
2024-03-13 12:25 ` dpdklab
2024-03-13 12:25 ` dpdklab
2024-03-13 12:25 ` dpdklab
2024-03-13 12:25 ` dpdklab
2024-03-13 12:26 ` dpdklab
2024-03-13 12:26 ` dpdklab
2024-03-13 12:27 ` dpdklab
2024-03-13 12:27 ` dpdklab
2024-03-13 12:28 ` dpdklab
2024-03-13 12:28 ` dpdklab
2024-03-13 12:28 ` dpdklab
2024-03-13 12:28 ` dpdklab
2024-03-13 12:28 ` dpdklab
2024-03-13 12:29 ` dpdklab
2024-03-13 12:29 ` dpdklab
2024-03-13 12:29 ` dpdklab
2024-03-13 12:30 ` dpdklab
2024-03-13 12:30 ` dpdklab
2024-03-13 12:31 ` dpdklab
2024-03-13 12:31 ` dpdklab
2024-03-13 12:31 ` dpdklab
2024-03-13 12:31 ` dpdklab
2024-03-13 12:32 ` dpdklab
2024-03-13 12:32 ` dpdklab
2024-03-13 12:32 ` dpdklab
2024-03-13 12:32 ` dpdklab
2024-03-13 12:33 ` dpdklab
2024-03-13 12:33 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:37 ` dpdklab
2024-03-13 12:37 ` dpdklab
2024-03-13 12:41 ` dpdklab
2024-03-13 12:50 ` dpdklab
2024-03-13 12:50 ` dpdklab
2024-03-13 12:58 ` dpdklab
2024-03-13 13:48 ` dpdklab
2024-03-13 19:05 ` dpdklab
2024-03-13 19:06 ` dpdklab
2024-03-13 19:09 ` dpdklab
2024-03-13 19:11 ` dpdklab
2024-03-13 19:12 ` dpdklab
2024-03-13 19:13 ` dpdklab
2024-03-13 19:14 ` dpdklab
2024-03-13 19:16 ` dpdklab
2024-03-13 19:17 ` dpdklab
2024-03-13 19:24 ` dpdklab
2024-03-13 19:24 ` dpdklab
2024-03-13 19:29 ` dpdklab
2024-03-17 2:44 ` dpdklab
2024-03-17 3:20 ` dpdklab
2024-03-17 9:40 ` dpdklab
2024-03-17 10:20 ` 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=202403130944.42D9iUHw4181943@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).