From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133731 [PATCH] maintainers: update for mempool library
Date: Thu, 2 Nov 2023 00:01:46 +0800 [thread overview]
Message-ID: <202311011601.3A1G1kmE1206143@localhost.localdomain> (raw)
In-Reply-To: <20231101162018.42733-1-mb@smartsharesystems.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/133731
_Compilation OK_
Submitter: Morten Brørup <mb@smartsharesystems.com>
Date: Wed, 1 Nov 2023 17:20:18 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 1025bd1c24b1be70e028c7ba0595782bce75fcc6
133731 --> 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-11-01 16:22 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231101162018.42733-1-mb@smartsharesystems.com>
2023-11-01 16:01 ` qemudev [this message]
2023-11-01 16:06 ` qemudev
2023-11-01 16:21 ` checkpatch
2023-11-01 17:39 ` |FAILURE| " 0-day Robot
2023-11-01 19:09 |SUCCESS| " dpdklab
2023-11-01 19:13 dpdklab
2023-11-01 19:19 dpdklab
2023-11-01 19:25 dpdklab
2023-11-01 19:40 dpdklab
2023-11-01 19:48 dpdklab
2023-11-01 19:49 dpdklab
2023-11-01 20:09 dpdklab
2023-11-01 20:10 dpdklab
2023-11-01 20:20 dpdklab
2023-11-01 21:29 dpdklab
2023-11-01 22:00 dpdklab
2023-11-01 22:01 dpdklab
2023-11-01 22:03 dpdklab
2023-11-01 22:03 dpdklab
2023-11-01 22:04 dpdklab
2023-11-01 22:04 dpdklab
2023-11-01 22:05 dpdklab
2023-11-01 22:05 dpdklab
2023-11-01 22:05 dpdklab
2023-11-01 22:05 dpdklab
2023-11-01 22:06 dpdklab
2023-11-01 22:06 dpdklab
2023-11-01 22:06 dpdklab
2023-11-01 22:07 dpdklab
2023-11-01 22:07 dpdklab
2023-11-01 22:08 dpdklab
2023-11-01 22:08 dpdklab
2023-11-01 22:08 dpdklab
2023-11-01 22:09 dpdklab
2023-11-01 22:09 dpdklab
2023-11-01 22:09 dpdklab
2023-11-01 22:10 dpdklab
2023-11-01 22:10 dpdklab
2023-11-01 22:10 dpdklab
2023-11-01 22:11 dpdklab
2023-11-01 22:12 dpdklab
2023-11-01 22:12 dpdklab
2023-11-01 22:12 dpdklab
2023-11-01 22:13 dpdklab
2023-11-01 22:18 dpdklab
2023-11-01 22:18 dpdklab
2023-11-01 22:19 dpdklab
2023-11-01 22:19 dpdklab
2023-11-01 22:19 dpdklab
2023-11-01 22:20 dpdklab
2023-11-01 22:21 dpdklab
2023-11-01 22:22 dpdklab
2023-11-01 22:22 dpdklab
2023-11-01 22:26 dpdklab
2023-11-01 22:28 dpdklab
2023-11-01 22:29 dpdklab
2023-11-01 22:50 dpdklab
2023-11-01 23:15 dpdklab
2023-11-02 2:08 dpdklab
2023-11-02 7:10 dpdklab
2023-11-02 16:48 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=202311011601.3A1G1kmE1206143@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).