From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133174 [PATCH v2] eal: support lcore usage ratio
Date: Mon, 23 Oct 2023 20:13:23 +0800 [thread overview]
Message-ID: <202310231213.39NCDN4r1640043@localhost.localdomain> (raw)
In-Reply-To: <20231023122929.54028-1-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/133174
_Compilation OK_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Mon, 23 Oct 2023 12:29:29 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 2cd2cf0cc53a508c4bd951a980ec534a646260de
133174 --> 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-10-23 12:34 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231023122929.54028-1-fengchengwen@huawei.com>
2023-10-23 12:13 ` qemudev [this message]
2023-10-23 12:17 ` qemudev
2023-10-23 12:34 ` checkpatch
2023-10-23 14:25 ` 0-day Robot
2023-10-23 13:58 |SUCCESS| pw133174 [PATCH] [v2] " dpdklab
2023-10-23 14:00 dpdklab
2023-10-23 14:01 dpdklab
2023-10-23 14:02 dpdklab
2023-10-23 14:03 dpdklab
2023-10-23 14:05 dpdklab
2023-10-23 14:05 dpdklab
2023-10-23 14:20 dpdklab
2023-10-23 14:21 dpdklab
2023-10-23 14:21 dpdklab
2023-10-23 14:22 dpdklab
2023-10-23 14:22 dpdklab
2023-10-23 14:22 dpdklab
2023-10-23 14:23 dpdklab
2023-10-23 14:23 dpdklab
2023-10-23 14:23 dpdklab
2023-10-23 14:23 dpdklab
2023-10-23 14:24 dpdklab
2023-10-23 14:24 dpdklab
2023-10-23 14:24 dpdklab
2023-10-23 14:25 dpdklab
2023-10-23 14:27 dpdklab
2023-10-23 14:27 dpdklab
2023-10-23 14:28 dpdklab
2023-10-23 14:29 dpdklab
2023-10-23 14:29 dpdklab
2023-10-23 14:29 dpdklab
2023-10-23 14:29 dpdklab
2023-10-23 14:30 dpdklab
2023-10-23 14:31 dpdklab
2023-10-23 14:32 dpdklab
2023-10-23 14:34 dpdklab
2023-10-23 14:37 dpdklab
2023-10-23 14:40 dpdklab
2023-10-23 14:41 dpdklab
2023-10-23 14:43 dpdklab
2023-10-23 14:44 dpdklab
2023-10-23 14:44 dpdklab
2023-10-23 14:45 dpdklab
2023-10-23 14:47 dpdklab
2023-10-23 14:47 dpdklab
2023-10-23 14:48 dpdklab
2023-10-23 14:51 dpdklab
2023-10-23 14:51 dpdklab
2023-10-23 14:52 dpdklab
2023-10-23 14:54 dpdklab
2023-10-23 14:54 dpdklab
2023-10-23 14:58 dpdklab
2023-10-23 14:58 dpdklab
2023-10-23 14:59 dpdklab
2023-10-23 15:00 dpdklab
2023-10-23 15:31 dpdklab
2023-10-23 16:09 dpdklab
2023-10-23 17:59 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=202310231213.39NCDN4r1640043@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).