From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw145800 [PATCH] net/mlx5: fix potential memory leak in meter
Date: Sat, 12 Oct 2024 15:01:13 +0800 [thread overview]
Message-ID: <202410120701.49C71D9R881442@localhost.localdomain> (raw)
In-Reply-To: <20241012072641.3396372-1-shunh@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/145800
_Compilation OK_
Submitter: Shun Hao <shunh@nvidia.com>
Date: Sat, 12 Oct 2024 10:26:40 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 92f33d7016a5dfd0fc8ee95607db9671af7256a7
145800 --> 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-12 7:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241012072641.3396372-1-shunh@nvidia.com>
2024-10-12 7:01 ` qemudev [this message]
2024-10-12 7:05 ` qemudev
2024-10-12 7:27 ` |WARNING| " checkpatch
2024-10-12 8:22 ` |SUCCESS| " 0-day Robot
2024-10-13 4:19 ` |SUCCESS| pw145800 [PATCH] net/mlx5: fix potential memory leak in me dpdklab
2024-10-13 4:34 ` dpdklab
2024-10-13 4:38 ` dpdklab
2024-10-13 4:48 ` dpdklab
2024-10-13 4:51 ` dpdklab
2024-10-13 6:15 ` dpdklab
2024-10-13 6:28 ` dpdklab
2024-10-13 6:36 ` dpdklab
2024-10-13 7:59 ` |PENDING| " dpdklab
2024-10-13 8:01 ` dpdklab
2024-10-13 8:05 ` |SUCCESS| " dpdklab
2024-10-13 8:07 ` dpdklab
2024-10-13 8:08 ` dpdklab
2024-10-13 8:14 ` |PENDING| " dpdklab
2024-10-13 9:54 ` dpdklab
2024-10-13 10:47 ` |SUCCESS| " dpdklab
2024-10-13 10:50 ` dpdklab
2024-10-13 10:53 ` dpdklab
2024-10-13 12:07 ` dpdklab
2024-10-13 12:59 ` dpdklab
2024-10-21 8:49 ` dpdklab
2024-10-21 11:49 ` dpdklab
2024-10-22 4:04 ` dpdklab
2024-10-23 3:28 ` 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=202410120701.49C71D9R881442@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).