From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140139 [PATCH] mempool: dump includes list of memory chunks
Date: Thu, 16 May 2024 16:33:55 +0800 [thread overview]
Message-ID: <202405160833.44G8XtfO057874@localhost.localdomain> (raw)
In-Reply-To: <20240516085940.61119-1-mb@smartsharesystems.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140139
_Compilation OK_
Submitter: Morten Brørup <mb@smartsharesystems.com>
Date: Thu, 16 May 2024 10:59:40 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 884f83ccf74b5364430d3b21c653d5f6e359e091
140139 --> 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-05-16 9:01 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240516085940.61119-1-mb@smartsharesystems.com>
2024-05-16 8:33 ` qemudev [this message]
2024-05-16 8:38 ` qemudev
2024-05-16 8:59 ` checkpatch
2024-05-16 10:04 ` 0-day Robot
2024-05-16 16:59 ` |SUCCESS| pw140139 [PATCH] mempool: dump includes list of memory chu dpdklab
2024-05-16 17:00 ` dpdklab
2024-05-16 17:02 ` dpdklab
2024-05-16 17:03 ` dpdklab
2024-05-16 17:03 ` dpdklab
2024-05-16 17:03 ` dpdklab
2024-05-16 17:28 ` dpdklab
2024-05-16 17:28 ` dpdklab
2024-05-16 17:29 ` dpdklab
2024-05-16 17:29 ` dpdklab
2024-05-16 17:29 ` dpdklab
2024-05-16 17:29 ` dpdklab
2024-05-16 17:30 ` dpdklab
2024-05-16 17:30 ` dpdklab
2024-05-16 17:30 ` dpdklab
2024-05-16 17:30 ` dpdklab
2024-05-16 17:30 ` dpdklab
2024-05-16 17:31 ` dpdklab
2024-05-16 17:31 ` dpdklab
2024-05-16 17:31 ` dpdklab
2024-05-16 17:31 ` dpdklab
2024-05-16 17:31 ` dpdklab
2024-05-16 17:32 ` dpdklab
2024-05-16 17:32 ` dpdklab
2024-05-16 17:33 ` dpdklab
2024-05-16 17:33 ` dpdklab
2024-05-16 17:34 ` dpdklab
2024-05-16 17:34 ` dpdklab
2024-05-16 17:35 ` dpdklab
2024-05-16 17:35 ` dpdklab
2024-05-16 17:35 ` dpdklab
2024-05-16 17:35 ` dpdklab
2024-05-16 17:36 ` dpdklab
2024-05-16 17:36 ` dpdklab
2024-05-16 17:36 ` dpdklab
2024-05-16 17:36 ` dpdklab
2024-05-16 17:37 ` dpdklab
2024-05-16 17:37 ` dpdklab
2024-05-16 17:37 ` dpdklab
2024-05-16 17:37 ` dpdklab
2024-05-16 17:38 ` dpdklab
2024-05-16 17:38 ` dpdklab
2024-05-16 17:38 ` dpdklab
2024-05-16 17:38 ` dpdklab
2024-05-16 17:39 ` dpdklab
2024-05-16 17:39 ` dpdklab
2024-05-16 17:39 ` dpdklab
2024-05-16 17:39 ` dpdklab
2024-05-16 17:39 ` dpdklab
2024-05-16 17:39 ` dpdklab
2024-05-16 17:40 ` dpdklab
2024-05-16 17:40 ` dpdklab
2024-05-16 17:40 ` dpdklab
2024-05-16 17:40 ` dpdklab
2024-05-16 17:40 ` dpdklab
2024-05-16 17:41 ` dpdklab
2024-05-16 17:41 ` dpdklab
2024-05-16 17:41 ` dpdklab
2024-05-16 17:41 ` dpdklab
2024-05-16 17:41 ` dpdklab
2024-05-16 17:41 ` dpdklab
2024-05-16 17:42 ` dpdklab
2024-05-16 17:42 ` dpdklab
2024-05-16 17:42 ` dpdklab
2024-05-16 17:42 ` dpdklab
2024-05-16 17:42 ` dpdklab
2024-05-16 17:44 ` dpdklab
2024-05-16 17:45 ` dpdklab
2024-05-16 17:45 ` dpdklab
2024-05-16 17:47 ` dpdklab
2024-05-16 17:47 ` dpdklab
2024-05-16 17:48 ` dpdklab
2024-05-16 17:51 ` dpdklab
2024-05-16 17:51 ` dpdklab
2024-05-16 17:52 ` dpdklab
2024-05-16 17:55 ` dpdklab
2024-05-16 17:59 ` dpdklab
2024-05-16 18:05 ` dpdklab
2024-05-16 18:06 ` dpdklab
2024-05-16 18:07 ` dpdklab
2024-05-16 18:11 ` dpdklab
2024-05-16 18:24 ` dpdklab
2024-05-16 18:37 ` dpdklab
2024-05-16 18:42 ` dpdklab
2024-05-16 18:45 ` 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=202405160833.44G8XtfO057874@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).