From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137355 [PATCH v2] net/mlx5: fix VLAN handling in meter split
Date: Tue, 27 Feb 2024 21:36:50 +0800 [thread overview]
Message-ID: <202402271336.41RDao5H4015107@localhost.localdomain> (raw)
In-Reply-To: <20240227135816.135279-1-dsosnowski@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137355
_Compilation OK_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Tue, 27 Feb 2024 14:58:15 +0100
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 298ef95d4ef2a53ea39e94c2326fe2fdf6b91203
137355 --> 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-27 14:01 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227135816.135279-1-dsosnowski@nvidia.com>
2024-02-27 13:36 ` qemudev [this message]
2024-02-27 13:41 ` qemudev
2024-02-27 13:59 ` checkpatch
2024-02-27 15:04 ` 0-day Robot
2024-02-27 22:10 ` |SUCCESS| pw137355 [PATCH] [v2] net/mlx5: fix VLAN handling in meter dpdklab
2024-02-27 22:11 ` dpdklab
2024-02-27 22:12 ` dpdklab
2024-02-27 22:12 ` dpdklab
2024-02-27 22:13 ` dpdklab
2024-02-27 22:13 ` dpdklab
2024-02-27 22:16 ` dpdklab
2024-02-27 22:18 ` dpdklab
2024-02-27 22:20 ` dpdklab
2024-02-27 22:20 ` dpdklab
2024-02-27 22:21 ` dpdklab
2024-02-27 22:21 ` dpdklab
2024-02-27 22:22 ` dpdklab
2024-02-27 22:24 ` dpdklab
2024-02-27 22:26 ` dpdklab
2024-02-27 22:30 ` dpdklab
2024-02-27 22:31 ` dpdklab
2024-02-27 22:31 ` dpdklab
2024-02-27 22:31 ` dpdklab
2024-02-27 22:32 ` dpdklab
2024-02-27 22:39 ` dpdklab
2024-02-27 22:39 ` dpdklab
2024-02-27 22:39 ` dpdklab
2024-02-27 22:40 ` dpdklab
2024-02-27 22:41 ` dpdklab
2024-02-27 22:45 ` dpdklab
2024-02-27 22:47 ` dpdklab
2024-02-27 22:47 ` dpdklab
2024-02-27 22:47 ` dpdklab
2024-02-27 22:48 ` dpdklab
2024-02-27 22:48 ` dpdklab
2024-02-27 22:48 ` dpdklab
2024-02-27 22:48 ` dpdklab
2024-02-27 22:49 ` dpdklab
2024-02-27 22:50 ` dpdklab
2024-02-27 22:51 ` dpdklab
2024-02-27 22:54 ` dpdklab
2024-02-27 22:57 ` dpdklab
2024-02-27 23:04 ` dpdklab
2024-02-27 23:04 ` dpdklab
2024-02-27 23:12 ` dpdklab
2024-02-27 23:43 ` dpdklab
2024-02-28 0:23 ` dpdklab
2024-02-28 1:30 ` dpdklab
2024-02-28 5:16 ` dpdklab
2024-02-28 9:05 ` dpdklab
2024-02-28 9:14 ` dpdklab
2024-02-28 15:28 ` dpdklab
2024-02-29 1:51 ` dpdklab
2024-02-29 13:02 ` dpdklab
2024-02-29 13:05 ` dpdklab
2024-02-29 13:12 ` dpdklab
2024-02-29 13:18 ` 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=202402271336.41RDao5H4015107@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).