From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148569 [PATCH] net/mlx5: fix the leak of action data list
Date: Mon, 18 Nov 2024 14:21:41 +0800 [thread overview]
Message-ID: <202411180621.4AI6Lf9B1991312@localhost.localdomain> (raw)
In-Reply-To: <20241118065259.250538-1-bingz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148569
_Compilation OK_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Mon, 18 Nov 2024 08:52:59 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 969e73b20419912ba9dd22e86a43a5ebfbabeca2
148569 --> 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-18 6:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241118065259.250538-1-bingz@nvidia.com>
2024-11-18 6:21 ` qemudev [this message]
2024-11-18 6:26 ` qemudev
2024-11-18 6:54 ` |WARNING| " checkpatch
2024-11-18 7:44 ` |SUCCESS| " 0-day Robot
2024-11-18 8:00 ` |SUCCESS| pw148569 [PATCH] net/mlx5: fix the leak of action data lis dpdklab
2024-11-18 8:04 ` |PENDING| " dpdklab
2024-11-18 8:08 ` |SUCCESS| " dpdklab
2024-11-18 8:11 ` dpdklab
2024-11-18 8:13 ` dpdklab
2024-11-18 8:14 ` |PENDING| " dpdklab
2024-11-18 8:17 ` |SUCCESS| " dpdklab
2024-11-18 8:22 ` |PENDING| " dpdklab
2024-11-18 8:30 ` |SUCCESS| " dpdklab
2024-11-18 8:42 ` |PENDING| " dpdklab
2024-11-18 8:44 ` |SUCCESS| " dpdklab
2024-11-18 8:59 ` dpdklab
2024-11-18 9:19 ` dpdklab
2024-11-18 9:52 ` dpdklab
2024-11-18 10:10 ` |WARNING| " dpdklab
2024-11-18 10:16 ` |SUCCESS| " dpdklab
2024-11-18 11:21 ` 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=202411180621.4AI6Lf9B1991312@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).