From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw155813 [PATCH v2] net/mlx5: fix connection tracking state item validation
Date: Tue, 12 Aug 2025 20:15:22 +0800 [thread overview]
Message-ID: <202508121215.57CCFMGc803470@localhost.localdomain> (raw)
In-Reply-To: <20250812124630.2916225-1-14pwcse1224@uetpeshawar.edu.pk>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/155813
_Compilation OK_
Submitter: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
Date: Tue, 12 Aug 2025 08:46:30 -0400
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 507dd6a18ebcae562fd0539bddbf499a4b891bb7
155813 --> 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:[~2025-08-12 12:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250812124630.2916225-1-14pwcse1224@uetpeshawar.edu.pk>
2025-08-12 12:15 ` qemudev [this message]
2025-08-12 12:20 ` qemudev
2025-08-12 12:45 ` |WARNING| " checkpatch
2025-08-12 13:39 ` |SUCCESS| " 0-day Robot
2025-08-13 2:58 ` |PENDING| pw155813 [PATCH] [v2] net/mlx5: fix connection tracking st dpdklab
2025-08-13 3:00 ` |SUCCESS| " dpdklab
2025-08-13 3:03 ` dpdklab
2025-08-13 3:07 ` |PENDING| " dpdklab
2025-08-13 3:17 ` |SUCCESS| " dpdklab
2025-08-13 3:17 ` dpdklab
2025-08-13 3:21 ` dpdklab
2025-08-13 3:22 ` dpdklab
2025-08-13 3:25 ` dpdklab
2025-08-13 3:30 ` dpdklab
2025-08-13 3:37 ` dpdklab
2025-08-13 3:41 ` dpdklab
2025-08-13 3:46 ` dpdklab
2025-08-13 4:07 ` dpdklab
2025-08-13 4:16 ` dpdklab
2025-08-13 4:32 ` dpdklab
2025-08-13 12:50 ` dpdklab
2025-08-13 12:50 ` 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=202508121215.57CCFMGc803470@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).