From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148638 [PATCH] net/mlx5/hws: allow vport action to wire in RX flow
Date: Tue, 19 Nov 2024 21:59:11 +0800 [thread overview]
Message-ID: <202411191359.4AJDxB473318054@localhost.localdomain> (raw)
In-Reply-To: <20241119142915.1889997-1-igozlan@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148638
_Compilation OK_
Submitter: Itamar Gozlan <igozlan@nvidia.com>
Date: Tue, 19 Nov 2024 16:29:15 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 37dda90ee15b7098bc48356868a87d34f727eecc
148638 --> 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-11-19 14:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241119142915.1889997-1-igozlan@nvidia.com>
2024-11-19 13:59 ` qemudev [this message]
2024-11-19 14:03 ` qemudev
2024-11-19 14:30 ` checkpatch
2024-11-19 14:58 ` |PENDING| pw148638 [PATCH] net/mlx5/hws: allow vport action to wire dpdklab
2024-11-19 15:03 ` |SUCCESS| " dpdklab
2024-11-19 15:06 ` |PENDING| " dpdklab
2024-11-19 15:08 ` |SUCCESS| " dpdklab
2024-11-19 15:19 ` dpdklab
2024-11-19 15:24 ` |SUCCESS| pw148638 [PATCH] net/mlx5/hws: allow vport action to wire in RX flow 0-day Robot
2024-11-19 15:27 ` |SUCCESS| pw148638 [PATCH] net/mlx5/hws: allow vport action to wire dpdklab
2024-11-19 15:27 ` dpdklab
2024-11-19 15:28 ` dpdklab
2024-11-19 15:31 ` dpdklab
2024-11-19 15:40 ` dpdklab
2024-11-19 15:44 ` dpdklab
2024-11-19 15:48 ` dpdklab
2024-11-19 18:02 ` 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=202411191359.4AJDxB473318054@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).