From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133185 [PATCH v3] eal: support lcore usage ratio
Date: Mon, 23 Oct 2023 20:35:00 +0800 [thread overview]
Message-ID: <202310231235.39NCZ0Gw1750812@localhost.localdomain> (raw)
In-Reply-To: <20231023125132.4216-1-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/133185
_Compilation OK_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Mon, 23 Oct 2023 12:51:32 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 2cd2cf0cc53a508c4bd951a980ec534a646260de
133185 --> 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:56 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231023125132.4216-1-fengchengwen@huawei.com>
2023-10-23 12:35 ` qemudev [this message]
2023-10-23 12:39 ` qemudev
2023-10-23 12:55 ` checkpatch
2023-10-23 14:26 ` 0-day Robot
2023-10-23 16:38 |SUCCESS| pw133185 [PATCH] [v3] " dpdklab
2023-10-23 16:41 dpdklab
2023-10-23 16:41 dpdklab
2023-10-23 16:41 dpdklab
2023-10-23 16:46 dpdklab
2023-10-23 16:46 dpdklab
2023-10-23 16:51 dpdklab
2023-10-23 16:51 dpdklab
2023-10-23 16:51 dpdklab
2023-10-23 16:51 dpdklab
2023-10-23 16:51 dpdklab
2023-10-23 16:54 dpdklab
2023-10-23 17:19 dpdklab
2023-10-23 17:19 dpdklab
2023-10-23 17:20 dpdklab
2023-10-23 17:21 dpdklab
2023-10-23 17:21 dpdklab
2023-10-23 17:22 dpdklab
2023-10-23 17:22 dpdklab
2023-10-23 17:22 dpdklab
2023-10-23 17:23 dpdklab
2023-10-23 17:23 dpdklab
2023-10-23 17:23 dpdklab
2023-10-23 17:23 dpdklab
2023-10-23 17:23 dpdklab
2023-10-23 17:24 dpdklab
2023-10-23 17:24 dpdklab
2023-10-23 17:25 dpdklab
2023-10-23 17:25 dpdklab
2023-10-23 17:25 dpdklab
2023-10-23 17:28 dpdklab
2023-10-23 17:32 dpdklab
2023-10-23 17:33 dpdklab
2023-10-23 17:34 dpdklab
2023-10-23 17:34 dpdklab
2023-10-23 17:35 dpdklab
2023-10-23 17:36 dpdklab
2023-10-23 17:43 dpdklab
2023-10-23 17:44 dpdklab
2023-10-23 17:49 dpdklab
2023-10-23 17:50 dpdklab
2023-10-23 17:50 dpdklab
2023-10-23 17:51 dpdklab
2023-10-23 17:51 dpdklab
2023-10-23 17:53 dpdklab
2023-10-23 17:53 dpdklab
2023-10-23 17:54 dpdklab
2023-10-23 17:54 dpdklab
2023-10-23 17:54 dpdklab
2023-10-23 17:56 dpdklab
2023-10-23 17:57 dpdklab
2023-10-23 17:57 dpdklab
2023-10-23 17:58 dpdklab
2023-10-23 18:24 dpdklab
2023-10-23 18:44 dpdklab
2023-10-23 20:08 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=202310231235.39NCZ0Gw1750812@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).