From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw159354 [PATCH 1/1] net/mlx5: fix memoy leak after device spawn failure
Date: Thu, 18 Dec 2025 18:02:27 +0800 [thread overview]
Message-ID: <202512181002.5BIA2RsM2658743@localhost.localdomain> (raw)
In-Reply-To: <1766050280-21036-1-git-send-email-wangyunjian@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/159354
_Compilation OK_
Submitter: Yunjian Wang <wangyunjian@huawei.com>
Date: Thu, 18 Dec 2025 17:31:20 +0800
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 2815d5065694eb9d0b43c312d17a00d2356e36f1
159354 --> 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 prev parent reply other threads:[~2025-12-18 10:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1766050280-21036-1-git-send-email-wangyunjian@huawei.com>
2025-12-18 9:30 ` |WARNING| " checkpatch
2025-12-18 10:02 ` qemudev [this message]
2025-12-18 10:07 ` |SUCCESS| " qemudev
2025-12-18 10:49 ` 0-day Robot
2025-12-18 10:49 ` 0-day Robot
2025-12-18 11:31 ` |SUCCESS| pw159354 [PATCH] [1/1] net/mlx5: fix memoy leak after devi dpdklab
2025-12-18 11:36 ` dpdklab
2025-12-18 11:37 ` |PENDING| " dpdklab
2025-12-18 11:41 ` |SUCCESS| " dpdklab
2025-12-18 11:48 ` |PENDING| " dpdklab
2025-12-18 11:52 ` |SUCCESS| " dpdklab
2025-12-18 11:55 ` dpdklab
2025-12-18 11:55 ` dpdklab
2025-12-18 12:10 ` |PENDING| " dpdklab
2025-12-18 12:14 ` |SUCCESS| " dpdklab
2025-12-18 12:26 ` |PENDING| " dpdklab
2025-12-18 12:51 ` |SUCCESS| " dpdklab
2025-12-18 12:57 ` dpdklab
2025-12-18 12:59 ` dpdklab
2025-12-18 15:11 ` dpdklab
2025-12-18 15:53 ` dpdklab
2025-12-19 1:23 ` 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=202512181002.5BIA2RsM2658743@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).