From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125136 [PATCH] net/iavf: fix VLAN Tx in AVX512
Date: Wed, 15 Mar 2023 16:32:04 +0800 [thread overview]
Message-ID: <202303150832.32F8W4ki3396661@localhost.localdomain> (raw)
In-Reply-To: <20230315084617.432821-1-zhichaox.zeng@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125136
_Compilation OK_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Wed, 15 Mar 2023 16:46:17 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: baf13c3135d0c5998fff7edc23fb89412dc89246
125136 --> 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:[~2023-03-15 8:45 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230315084617.432821-1-zhichaox.zeng@intel.com>
2023-03-15 8:32 ` qemudev [this message]
2023-03-15 8:36 ` qemudev
2023-03-15 8:42 ` checkpatch
2023-03-15 10:39 ` 0-day Robot
2023-03-15 10:07 dpdklab
2023-03-15 10:07 dpdklab
2023-03-15 10:13 dpdklab
2023-03-15 10:15 dpdklab
2023-03-15 10:16 dpdklab
2023-03-15 10:20 dpdklab
2023-03-15 10:30 dpdklab
2023-03-15 10:35 dpdklab
2023-03-15 10:39 dpdklab
2023-03-15 10:42 dpdklab
2023-03-15 10:46 dpdklab
2023-03-15 10:49 dpdklab
2023-03-15 10:56 dpdklab
2023-03-15 10:58 dpdklab
2023-03-15 10:59 dpdklab
2023-03-15 11:01 dpdklab
2023-03-15 11:02 dpdklab
2023-03-15 11:08 dpdklab
2023-03-15 11:14 dpdklab
2023-03-15 11:18 dpdklab
2023-03-15 11:19 dpdklab
2023-03-15 11:24 dpdklab
2023-03-15 11:39 dpdklab
2023-03-15 11:40 dpdklab
2023-03-15 11:52 dpdklab
2023-03-15 11:59 dpdklab
2023-03-15 12:01 dpdklab
2023-03-15 12:14 dpdklab
2023-03-15 12:30 dpdklab
2023-03-15 12:46 dpdklab
2023-03-15 14:01 dpdklab
2023-03-15 15:20 dpdklab
2023-03-17 14:49 dpdklab
2023-03-17 17:12 dpdklab
2023-03-18 14:08 dpdklab
2023-03-18 20:59 dpdklab
2023-03-18 21:08 dpdklab
2023-03-18 21:11 dpdklab
2023-03-18 21:14 dpdklab
2023-03-18 21:18 dpdklab
2023-03-18 21:22 dpdklab
2023-03-18 21:29 dpdklab
2023-03-18 21:38 dpdklab
2023-03-18 21:40 dpdklab
2023-03-18 21:44 dpdklab
2023-03-18 21:44 dpdklab
2023-03-18 21:45 dpdklab
2023-03-18 22:27 dpdklab
2023-03-18 23:34 dpdklab
2023-03-18 23:36 dpdklab
2023-03-18 23:43 dpdklab
2023-03-18 23:46 dpdklab
2023-03-18 23:53 dpdklab
2023-03-18 23:55 dpdklab
2023-03-19 0:00 dpdklab
2023-03-19 0:00 dpdklab
2023-03-19 0:09 dpdklab
2023-03-19 0:12 dpdklab
2023-03-19 0:15 dpdklab
2023-03-19 0:16 dpdklab
2023-03-19 0:17 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=202303150832.32F8W4ki3396661@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).