From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125009 [PATCH] app/crypto-perf: fix test file memory leak
Date: Fri, 10 Mar 2023 21:09:53 +0800 [thread overview]
Message-ID: <202303101309.32AD9rGB3432504@localhost.localdomain> (raw)
In-Reply-To: <20230310132017.6900-1-ciara.power@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125009
_Compilation OK_
Submitter: Ciara Power <ciara.power@intel.com>
Date: Fri, 10 Mar 2023 13:20:17 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 5028f207a4fa6d5cdd86019e43d2e2d80fa21ced
125009 --> 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:[~2023-03-10 13:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230310132017.6900-1-ciara.power@intel.com>
2023-03-10 13:09 ` qemudev [this message]
2023-03-10 13:13 ` qemudev
2023-03-10 13:21 ` checkpatch
2023-03-10 15:59 ` 0-day Robot
2023-03-10 19:46 dpdklab
2023-03-10 19:47 dpdklab
2023-03-10 19:48 dpdklab
2023-03-10 19:56 dpdklab
2023-03-10 19:57 dpdklab
2023-03-10 19:59 dpdklab
2023-03-10 20:00 dpdklab
2023-03-10 20:00 dpdklab
2023-03-10 20:04 dpdklab
2023-03-10 20:05 dpdklab
2023-03-10 20:11 dpdklab
2023-03-10 20:16 dpdklab
2023-03-10 20:24 dpdklab
2023-03-10 21:29 dpdklab
2023-03-11 8:57 dpdklab
2023-03-11 11:03 dpdklab
2023-03-11 22:42 dpdklab
2023-03-11 22:45 dpdklab
2023-03-11 22:46 dpdklab
2023-03-11 23:09 dpdklab
2023-03-11 23:13 dpdklab
2023-03-11 23:15 dpdklab
2023-03-11 23:17 dpdklab
2023-03-11 23:18 dpdklab
2023-03-11 23:19 dpdklab
2023-03-11 23:23 dpdklab
2023-03-11 23:26 dpdklab
2023-03-12 0:16 dpdklab
2023-03-12 0:16 dpdklab
2023-03-12 6:36 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=202303101309.32AD9rGB3432504@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).