From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw145018 [PATCH v3] app/proc-info: add rte_eal_cleanup() to avoid memory leak
Date: Fri, 4 Oct 2024 10:21:53 +0800 [thread overview]
Message-ID: <202410040221.4942LrN24113225@localhost.localdomain> (raw)
In-Reply-To: <20241004024903.209976-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/145018
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 3 Oct 2024 19:48:29 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 2b843cac232eb3f2fa79e4254e21766817e2019f
145018 --> 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-04 2:50 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241004024903.209976-1-stephen@networkplumber.org>
2024-10-04 2:21 ` qemudev [this message]
2024-10-04 2:26 ` qemudev
2024-10-04 2:50 ` |SUCCESS| pw145018 [PATCH v3] app/proc-info: add rte_eal_cleanup " checkpatch
2024-10-04 3:44 ` |SUCCESS| pw145018 [PATCH v3] app/proc-info: add rte_eal_cleanup() " 0-day Robot
2024-10-04 12:11 ` |SUCCESS| pw145018 [PATCH] [v3] app/proc-info: add rte_eal_cleanup() dpdklab
2024-10-04 12:17 ` dpdklab
2024-10-04 12:19 ` dpdklab
2024-10-04 12:26 ` dpdklab
2024-10-04 12:33 ` dpdklab
2024-10-04 12:34 ` dpdklab
2024-10-04 12:40 ` dpdklab
2024-10-04 12:50 ` dpdklab
2024-10-04 13:15 ` dpdklab
2024-10-04 13:17 ` dpdklab
2024-10-04 13:18 ` |PENDING| " dpdklab
2024-10-04 13:19 ` |SUCCESS| " dpdklab
2024-10-04 13:23 ` dpdklab
2024-10-04 13:30 ` dpdklab
2024-10-04 13:31 ` dpdklab
2024-10-04 13:34 ` dpdklab
2024-10-04 13:35 ` dpdklab
2024-10-04 13:42 ` |PENDING| " dpdklab
2024-10-04 13:51 ` dpdklab
2024-10-04 13:56 ` |SUCCESS| " dpdklab
2024-10-04 14:00 ` dpdklab
2024-10-04 14:01 ` dpdklab
2024-10-04 14:02 ` dpdklab
2024-10-04 14:03 ` dpdklab
2024-10-04 14:11 ` |PENDING| " dpdklab
2024-10-04 14:24 ` dpdklab
2024-10-04 14:49 ` dpdklab
2024-10-04 14:53 ` |SUCCESS| " dpdklab
2024-10-04 16:58 ` |PENDING| " dpdklab
2024-10-04 17:55 ` |SUCCESS| " dpdklab
2024-10-04 17:55 ` dpdklab
2024-10-04 18:01 ` dpdklab
2024-10-04 18:37 ` dpdklab
2024-10-04 18:37 ` dpdklab
2024-10-04 18:48 ` dpdklab
2024-10-04 18:57 ` dpdklab
2024-10-04 19:26 ` dpdklab
2024-10-04 20:38 ` dpdklab
2024-10-05 5:57 ` dpdklab
2024-10-05 11:47 ` 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=202410040221.4942LrN24113225@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).