From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124342 [PATCH v2] mem: fix displaying heap ID failed for heap info command
Date: Wed, 22 Feb 2023 15:40:18 +0800 [thread overview]
Message-ID: <202302220740.31M7eI8D1803067@localhost.localdomain> (raw)
In-Reply-To: <20230222074953.22715-1-lihuisong@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124342
_Compilation OK_
Submitter: Huisong Li <lihuisong@huawei.com>
Date: Wed, 22 Feb 2023 15:49:53 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7710b5d15a014872a3aaf646668dafa928ca8473
124342 --> 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-02-22 7:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230222074953.22715-1-lihuisong@huawei.com>
2023-02-22 7:40 ` qemudev [this message]
2023-02-22 7:44 ` qemudev
2023-02-22 7:51 ` checkpatch
2023-02-22 10:19 ` 0-day Robot
2023-02-22 8:17 |SUCCESS| pw124342 [PATCH] [v2] " dpdklab
2023-02-22 8:21 dpdklab
2023-02-22 8:21 dpdklab
2023-02-22 8:22 dpdklab
2023-02-22 8:28 dpdklab
2023-02-22 8:30 dpdklab
2023-02-22 8:33 dpdklab
2023-02-22 8:35 dpdklab
2023-02-22 8:37 dpdklab
2023-02-22 8:41 dpdklab
2023-02-22 13:10 dpdklab
2023-02-22 13:39 dpdklab
2023-02-22 13:57 dpdklab
2023-02-22 13:59 dpdklab
2023-02-22 14:01 dpdklab
2023-02-22 14:03 dpdklab
2023-02-22 14:05 dpdklab
2023-02-22 14:05 dpdklab
2023-02-22 14:09 dpdklab
2023-02-22 14:15 dpdklab
2023-02-22 14:21 dpdklab
2023-02-22 14:22 dpdklab
2023-02-22 14:24 dpdklab
2023-02-22 14:24 dpdklab
2023-02-22 18:10 dpdklab
2023-02-24 3:54 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=202302220740.31M7eI8D1803067@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).