From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138106 [PATCH v2] test/lcores: reduce cpu consumption
Date: Thu, 7 Mar 2024 21:54:18 +0800 [thread overview]
Message-ID: <202403071354.427DsIZl393779@localhost.localdomain> (raw)
In-Reply-To: <20240307141608.1450695-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138106
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Thu, 7 Mar 2024 15:16:06 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 19082c1fac430c74bb4b1c101edd12d88928e7c2
138106 --> 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:[~2024-03-07 14:19 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240307141608.1450695-1-david.marchand@redhat.com>
2024-03-07 13:54 ` qemudev [this message]
2024-03-07 13:58 ` qemudev
2024-03-07 14:16 ` checkpatch
2024-03-07 15:44 ` 0-day Robot
2024-03-07 16:21 ` |SUCCESS| pw138106 [PATCH] [v2] " dpdklab
2024-03-07 16:22 ` dpdklab
2024-03-07 16:23 ` dpdklab
2024-03-07 16:25 ` dpdklab
2024-03-07 16:30 ` dpdklab
2024-03-07 16:34 ` dpdklab
2024-03-07 16:35 ` dpdklab
2024-03-07 16:36 ` dpdklab
2024-03-07 16:59 ` dpdklab
2024-03-07 17:33 ` dpdklab
2024-03-07 17:41 ` dpdklab
2024-03-07 17:43 ` dpdklab
2024-03-07 17:44 ` dpdklab
2024-03-07 17:45 ` dpdklab
2024-03-07 17:49 ` dpdklab
2024-03-07 17:49 ` dpdklab
2024-03-07 17:50 ` dpdklab
2024-03-07 17:53 ` dpdklab
2024-03-07 18:01 ` dpdklab
2024-03-07 18:03 ` dpdklab
2024-03-07 18:03 ` dpdklab
2024-03-07 18:04 ` dpdklab
2024-03-07 18:04 ` dpdklab
2024-03-07 18:05 ` dpdklab
2024-03-07 18:06 ` dpdklab
2024-03-07 18:07 ` dpdklab
2024-03-07 18:07 ` dpdklab
2024-03-07 18:08 ` dpdklab
2024-03-07 18:08 ` dpdklab
2024-03-07 18:09 ` dpdklab
2024-03-07 18:10 ` dpdklab
2024-03-07 18:11 ` dpdklab
2024-03-07 18:11 ` dpdklab
2024-03-07 18:12 ` dpdklab
2024-03-07 18:13 ` dpdklab
2024-03-07 18:18 ` dpdklab
2024-03-07 18:18 ` dpdklab
2024-03-07 18:20 ` dpdklab
2024-03-07 18:20 ` dpdklab
2024-03-07 18:21 ` dpdklab
2024-03-07 18:22 ` dpdklab
2024-03-07 18:22 ` dpdklab
2024-03-07 18:23 ` dpdklab
2024-03-07 18:23 ` dpdklab
2024-03-07 18:24 ` dpdklab
2024-03-07 18:24 ` dpdklab
2024-03-07 18:25 ` dpdklab
2024-03-07 18:25 ` dpdklab
2024-03-07 18:25 ` dpdklab
2024-03-07 18:27 ` dpdklab
2024-03-07 18:29 ` dpdklab
2024-03-07 18:30 ` dpdklab
2024-03-07 18:30 ` dpdklab
2024-03-07 18:31 ` dpdklab
2024-03-07 18:31 ` dpdklab
2024-03-07 18:32 ` dpdklab
2024-03-07 18:33 ` dpdklab
2024-03-07 18:33 ` dpdklab
2024-03-07 18:35 ` dpdklab
2024-03-07 18:42 ` dpdklab
2024-03-07 18:43 ` dpdklab
2024-03-07 18:53 ` dpdklab
2024-03-07 18:53 ` dpdklab
2024-03-07 18:53 ` dpdklab
2024-03-07 18:54 ` dpdklab
2024-03-07 18:54 ` dpdklab
2024-03-07 18:55 ` dpdklab
2024-03-07 19:00 ` dpdklab
2024-03-07 19:06 ` dpdklab
2024-03-07 19:08 ` dpdklab
2024-03-07 19:08 ` dpdklab
2024-03-07 19:10 ` dpdklab
2024-03-07 19:11 ` dpdklab
2024-03-07 19:12 ` dpdklab
2024-03-07 19:12 ` dpdklab
2024-03-07 20:35 ` dpdklab
2024-03-07 22:11 ` dpdklab
2024-03-08 0:40 ` dpdklab
2024-03-08 7:56 ` dpdklab
2024-03-08 8:12 ` dpdklab
2024-03-08 8:37 ` dpdklab
2024-03-08 8:41 ` dpdklab
2024-03-12 5:21 ` dpdklab
2024-03-12 5:37 ` 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=202403071354.427DsIZl393779@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).