From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126074 [PATCH] reorder: introduce API to obtain memory footprint
Date: Fri, 14 Apr 2023 16:42:10 +0800 [thread overview]
Message-ID: <202304140842.33E8gASl855685@localhost.localdomain> (raw)
In-Reply-To: <20230414085251.272062-1-vfialko@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126074
_Compilation OK_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Fri, 14 Apr 2023 10:52:51 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd
126074 --> 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-04-14 8:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230414085251.272062-1-vfialko@marvell.com>
2023-04-14 8:42 ` qemudev [this message]
2023-04-14 8:46 ` qemudev
2023-04-14 8:54 ` checkpatch
2023-04-14 9:59 ` 0-day Robot
2023-04-14 11:26 dpdklab
2023-04-14 11:27 dpdklab
2023-04-14 11:31 dpdklab
2023-04-14 11:32 dpdklab
2023-04-14 11:32 dpdklab
2023-04-14 11:34 dpdklab
2023-04-14 11:39 dpdklab
2023-04-14 11:40 dpdklab
2023-04-14 11:48 dpdklab
2023-04-14 11:52 dpdklab
2023-04-14 12:02 dpdklab
2023-04-14 12:41 dpdklab
2023-04-14 12:42 dpdklab
2023-04-14 12:43 dpdklab
2023-04-14 12:45 dpdklab
2023-04-14 12:47 dpdklab
2023-04-14 12:50 dpdklab
2023-04-14 12:51 dpdklab
2023-04-14 12:53 dpdklab
2023-04-14 12:56 dpdklab
2023-04-14 13:02 dpdklab
2023-04-14 14:53 dpdklab
2023-04-14 16:12 dpdklab
2023-04-14 17:31 dpdklab
2023-04-14 17:32 dpdklab
2023-04-14 23:47 dpdklab
2023-04-14 23:51 dpdklab
2023-04-14 23:57 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=202304140842.33E8gASl855685@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).