From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw136573 [PATCH 1/1] net/mana: add vlan tagging support
Date: Fri, 9 Feb 2024 16:35:12 +0800 [thread overview]
Message-ID: <202402090835.4198ZCju1873016@localhost.localdomain> (raw)
In-Reply-To: <20240209085211.2643148-1-weh@microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/136573
_Compilation OK_
Submitter: Wei Hu <weh@microsoft.com>
Date: Fri, 9 Feb 2024 08:52:11 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 86e09318b9be354222de6407594caad182e21a8e
136573 --> 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-02-09 9:00 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240209085211.2643148-1-weh@microsoft.com>
2024-02-09 8:35 ` qemudev [this message]
2024-02-09 8:39 ` qemudev
2024-02-09 8:53 ` checkpatch
2024-02-09 9:44 ` 0-day Robot
2024-02-09 9:38 |SUCCESS| pw136573 [PATCH] [1/1] " dpdklab
2024-02-09 9:38 dpdklab
2024-02-09 9:38 dpdklab
2024-02-09 9:39 dpdklab
2024-02-09 9:39 dpdklab
2024-02-09 9:39 dpdklab
2024-02-09 9:39 dpdklab
2024-02-09 9:39 dpdklab
2024-02-09 9:40 dpdklab
2024-02-09 9:40 dpdklab
2024-02-09 9:40 dpdklab
2024-02-09 9:41 dpdklab
2024-02-09 9:41 dpdklab
2024-02-09 9:42 dpdklab
2024-02-09 9:42 dpdklab
2024-02-09 9:42 dpdklab
2024-02-09 9:43 dpdklab
2024-02-09 9:43 dpdklab
2024-02-09 9:44 dpdklab
2024-02-09 9:44 dpdklab
2024-02-09 9:45 dpdklab
2024-02-09 9:45 dpdklab
2024-02-09 9:45 dpdklab
2024-02-09 9:45 dpdklab
2024-02-09 9:45 dpdklab
2024-02-09 9:46 dpdklab
2024-02-09 9:46 dpdklab
2024-02-09 9:46 dpdklab
2024-02-09 9:47 dpdklab
2024-02-09 9:48 dpdklab
2024-02-09 9:48 dpdklab
2024-02-09 9:49 dpdklab
2024-02-09 9:49 dpdklab
2024-02-09 9:49 dpdklab
2024-02-09 9:49 dpdklab
2024-02-09 9:49 dpdklab
2024-02-09 9:49 dpdklab
2024-02-09 9:49 dpdklab
2024-02-09 9:49 dpdklab
2024-02-09 9:49 dpdklab
2024-02-09 9:51 dpdklab
2024-02-09 9:51 dpdklab
2024-02-09 9:51 dpdklab
2024-02-09 9:51 dpdklab
2024-02-09 9:51 dpdklab
2024-02-09 9:51 dpdklab
2024-02-09 9:51 dpdklab
2024-02-09 9:52 dpdklab
2024-02-09 9:52 dpdklab
2024-02-09 9:52 dpdklab
2024-02-09 9:52 dpdklab
2024-02-09 9:53 dpdklab
2024-02-09 9:53 dpdklab
2024-02-09 9:54 dpdklab
2024-02-09 9:54 dpdklab
2024-02-09 9:54 dpdklab
2024-02-09 9:54 dpdklab
2024-02-09 10:00 dpdklab
2024-02-09 10:11 dpdklab
2024-02-09 10:48 dpdklab
2024-02-09 11:02 dpdklab
2024-02-09 11:16 dpdklab
2024-02-09 11:29 dpdklab
2024-02-09 11:35 dpdklab
2024-02-09 12:04 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=202402090835.4198ZCju1873016@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).