From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123496 [PATCH] mem: fix displaying heap ID failed for heap info command
Date: Thu, 9 Feb 2023 10:56:58 +0800 [thread overview]
Message-ID: <202302090256.3192uwci3568411@localhost.localdomain> (raw)
In-Reply-To: <20230209030341.9697-1-lihuisong@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123496
_Compilation OK_
Submitter: Huisong Li <lihuisong@huawei.com>
Date: Thu, 9 Feb 2023 11:03:41 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: a0c837ad1fb5b6a8b10a284ffeb5f9e31bd8ff00
123496 --> 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-09 3:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230209030341.9697-1-lihuisong@huawei.com>
2023-02-09 2:56 ` qemudev [this message]
2023-02-09 3:00 ` qemudev
2023-02-09 3:05 ` |WARNING| " checkpatch
2023-02-09 3:59 ` |SUCCESS| " 0-day Robot
2023-02-09 3:33 dpdklab
2023-02-09 3:40 dpdklab
2023-02-09 3:43 dpdklab
2023-02-09 3:44 dpdklab
2023-02-09 3:44 dpdklab
2023-02-09 3:45 dpdklab
2023-02-09 3:47 dpdklab
2023-02-09 3:52 dpdklab
2023-02-09 3:54 dpdklab
2023-02-09 3:55 dpdklab
2023-02-09 3:56 dpdklab
2023-02-09 4:01 dpdklab
2023-02-09 4:08 dpdklab
2023-02-09 5:34 dpdklab
2023-02-10 6:45 dpdklab
2023-02-10 7:00 dpdklab
2023-02-10 7:05 dpdklab
2023-02-10 7:12 dpdklab
2023-02-10 7:15 dpdklab
2023-02-10 7:22 dpdklab
2023-02-10 7:24 dpdklab
2023-02-10 7:25 dpdklab
2023-02-10 7:33 dpdklab
2023-02-10 7:34 dpdklab
2023-02-10 7:39 dpdklab
2023-02-10 7:40 dpdklab
2023-02-10 7:42 dpdklab
2023-02-10 7:42 dpdklab
2023-02-11 13:49 dpdklab
2023-02-12 2:38 dpdklab
2023-02-12 7:38 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=202302090256.3192uwci3568411@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).