From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw146828 [PATCH v3] net/mlx5: fix potential memory leak in meter
Date: Wed, 23 Oct 2024 14:03:00 +0800 [thread overview]
Message-ID: <202410230603.49N630U1070596@localhost.localdomain> (raw)
In-Reply-To: <20241023062216.967742-1-shunh@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/146828
_Compilation OK_
Submitter: Shun Hao <shunh@nvidia.com>
Date: Wed, 23 Oct 2024 09:22:15 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: c4f029602e46450a0c51953c4607e53488244071
146828 --> 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-10-23 6:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241023062216.967742-1-shunh@nvidia.com>
2024-10-23 6:03 ` qemudev [this message]
2024-10-23 6:07 ` qemudev
2024-10-23 6:23 ` |WARNING| " checkpatch
2024-10-23 7:26 ` |SUCCESS| " 0-day Robot
2024-10-23 12:22 ` |SUCCESS| pw146828 [PATCH] [v3] net/mlx5: fix potential memory leak dpdklab
2024-10-23 17:50 ` dpdklab
2024-10-23 18:02 ` dpdklab
2024-10-23 19:19 ` dpdklab
2024-10-23 21:13 ` dpdklab
2024-10-24 7:07 ` dpdklab
2024-10-24 7:43 ` dpdklab
2024-10-25 1:34 ` |PENDING| " dpdklab
2024-10-25 5:44 ` |SUCCESS| " dpdklab
2024-10-25 6:06 ` dpdklab
2024-10-26 1:40 ` |PENDING| " dpdklab
2024-10-26 1:45 ` |SUCCESS| " dpdklab
2024-10-26 16:49 ` dpdklab
2024-10-27 15:11 ` dpdklab
2024-10-27 21:09 ` dpdklab
2024-10-28 5:49 ` dpdklab
2024-10-28 6:01 ` dpdklab
2024-11-01 22:24 ` dpdklab
2024-11-03 0:43 ` 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=202410230603.49N630U1070596@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).