From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw141125 [PATCH] eal: fix logs for '--lcores'
Date: Thu, 13 Jun 2024 23:47:58 +0800 [thread overview]
Message-ID: <202406131547.45DFlwJC340996@localhost.localdomain> (raw)
In-Reply-To: <20240613161429.168287-1-ktraynor@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/141125
_Compilation OK_
Submitter: Kevin Traynor <ktraynor@redhat.com>
Date: Thu, 13 Jun 2024 17:14:29 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 6484c847d4e48386904841d6b7062007f837dfb4
141125 --> 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-06-13 16:16 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240613161429.168287-1-ktraynor@redhat.com>
2024-06-13 15:47 ` qemudev [this message]
2024-06-13 15:52 ` qemudev
2024-06-13 16:16 ` checkpatch
2024-06-13 17:06 ` 0-day Robot
2024-06-13 22:05 ` dpdklab
2024-06-13 22:17 ` dpdklab
2024-06-13 22:18 ` dpdklab
2024-06-13 22:18 ` dpdklab
2024-06-13 22:19 ` dpdklab
2024-06-13 22:19 ` dpdklab
2024-06-13 22:20 ` dpdklab
2024-06-13 22:20 ` dpdklab
2024-06-13 22:20 ` dpdklab
2024-06-13 22:21 ` dpdklab
2024-06-13 22:21 ` dpdklab
2024-06-13 22:21 ` dpdklab
2024-06-13 22:22 ` dpdklab
2024-06-13 22:22 ` dpdklab
2024-06-13 22:23 ` dpdklab
2024-06-13 22:23 ` dpdklab
2024-06-13 22:23 ` dpdklab
2024-06-13 22:24 ` dpdklab
2024-06-13 22:24 ` dpdklab
2024-06-13 22:25 ` dpdklab
2024-06-13 22:25 ` dpdklab
2024-06-13 22:25 ` dpdklab
2024-06-13 22:25 ` dpdklab
2024-06-13 22:27 ` dpdklab
2024-06-13 22:28 ` dpdklab
2024-06-13 22:29 ` dpdklab
2024-06-13 22:29 ` dpdklab
2024-06-13 22:30 ` dpdklab
2024-06-13 22:30 ` dpdklab
2024-06-13 22:31 ` dpdklab
2024-06-13 22:31 ` dpdklab
2024-06-13 22:36 ` dpdklab
2024-06-13 22:38 ` dpdklab
2024-06-13 22:38 ` dpdklab
2024-06-13 22:40 ` dpdklab
2024-06-13 22:43 ` dpdklab
2024-06-13 22:45 ` dpdklab
2024-06-13 22:49 ` dpdklab
2024-06-13 22:50 ` dpdklab
2024-06-13 22:50 ` dpdklab
2024-06-13 22:53 ` dpdklab
2024-06-13 22:54 ` dpdklab
2024-06-13 22:55 ` dpdklab
2024-06-13 22:57 ` dpdklab
2024-06-13 23:00 ` dpdklab
2024-06-13 23:00 ` dpdklab
2024-06-13 23:01 ` dpdklab
2024-06-13 23:01 ` dpdklab
2024-06-13 23:02 ` dpdklab
2024-06-13 23:03 ` dpdklab
2024-06-13 23:03 ` dpdklab
2024-06-13 23:03 ` dpdklab
2024-06-13 23:06 ` dpdklab
2024-06-13 23:06 ` dpdklab
2024-06-13 23:07 ` dpdklab
2024-06-13 23:14 ` dpdklab
2024-06-13 23:15 ` dpdklab
2024-06-13 23:15 ` dpdklab
2024-06-13 23:15 ` dpdklab
2024-06-13 23:16 ` dpdklab
2024-06-13 23:16 ` dpdklab
2024-06-13 23:17 ` dpdklab
2024-06-13 23:24 ` dpdklab
2024-06-13 23:25 ` dpdklab
2024-06-13 23:27 ` dpdklab
2024-06-13 23:47 ` dpdklab
2024-06-13 23:47 ` dpdklab
2024-06-13 23:53 ` dpdklab
2024-06-13 23:54 ` dpdklab
2024-06-13 23:55 ` dpdklab
2024-06-13 23:56 ` dpdklab
2024-06-13 23:57 ` dpdklab
2024-06-13 23:58 ` dpdklab
2024-06-13 23:58 ` dpdklab
2024-06-13 23:59 ` dpdklab
2024-06-14 0:08 ` dpdklab
2024-06-14 0:16 ` dpdklab
2024-06-14 0:19 ` dpdklab
2024-06-14 0:20 ` dpdklab
2024-06-14 0:21 ` dpdklab
2024-06-14 0:22 ` dpdklab
2024-06-14 0:27 ` dpdklab
2024-06-14 0:30 ` dpdklab
2024-06-14 0:41 ` dpdklab
2024-06-14 0:42 ` dpdklab
2024-06-14 0:42 ` dpdklab
2024-06-14 0:44 ` dpdklab
2024-06-14 1:11 ` dpdklab
2024-06-14 1:13 ` dpdklab
2024-06-14 1:27 ` dpdklab
2024-06-14 1:31 ` dpdklab
2024-06-14 1:36 ` dpdklab
2024-06-14 1:45 ` dpdklab
2024-06-14 1:49 ` dpdklab
2024-06-14 1:52 ` dpdklab
2024-06-14 1:56 ` dpdklab
2024-06-14 2:20 ` 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=202406131547.45DFlwJC340996@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).