From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140342 [PATCH] eal: speed up dpdk init time
Date: Tue, 28 May 2024 13:48:12 +0800 [thread overview]
Message-ID: <202405280548.44S5mC3f3449370@localhost.localdomain> (raw)
In-Reply-To: <20240528061259.29528-1-changfengnan@bytedance.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140342
_Compilation OK_
Submitter: Fengnan Chang <changfengnan@bytedance.com>
Date: Tue, 28 May 2024 14:12:59 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 77e63757d2a0106a0cc519f5a82e2d749d16475a
140342 --> 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-05-28 6:16 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240528061259.29528-1-changfengnan@bytedance.com>
2024-05-28 5:48 ` qemudev [this message]
2024-05-28 5:52 ` qemudev
2024-05-28 6:14 ` |WARNING| " checkpatch
2024-05-28 7:03 ` |SUCCESS| " 0-day Robot
2024-05-28 7:29 ` dpdklab
2024-05-28 7:31 ` dpdklab
2024-05-28 7:36 ` dpdklab
2024-05-28 7:36 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:41 ` dpdklab
2024-05-28 7:41 ` dpdklab
2024-05-28 7:41 ` dpdklab
2024-05-28 7:41 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:44 ` dpdklab
2024-05-28 7:44 ` dpdklab
2024-05-28 7:44 ` dpdklab
2024-05-28 7:45 ` dpdklab
2024-05-28 7:45 ` dpdklab
2024-05-28 7:48 ` dpdklab
2024-05-28 7:49 ` dpdklab
2024-05-28 7:49 ` dpdklab
2024-05-28 7:49 ` dpdklab
2024-05-28 7:50 ` dpdklab
2024-05-28 7:50 ` dpdklab
2024-05-28 7:50 ` dpdklab
2024-05-28 7:51 ` dpdklab
2024-05-28 7:52 ` dpdklab
2024-05-28 7:52 ` dpdklab
2024-05-28 7:53 ` dpdklab
2024-05-28 7:53 ` dpdklab
2024-05-28 7:54 ` dpdklab
2024-05-28 7:55 ` dpdklab
2024-05-28 7:55 ` dpdklab
2024-05-28 7:55 ` dpdklab
2024-05-28 7:56 ` dpdklab
2024-05-28 7:56 ` dpdklab
2024-05-28 7:57 ` dpdklab
2024-05-28 7:58 ` dpdklab
2024-05-28 7:58 ` dpdklab
2024-05-28 8:00 ` dpdklab
2024-05-28 8:02 ` dpdklab
2024-05-28 8:33 ` dpdklab
2024-05-28 8:34 ` dpdklab
2024-05-28 8:55 ` dpdklab
2024-05-28 8:56 ` dpdklab
2024-05-28 8:57 ` dpdklab
2024-05-28 8:58 ` dpdklab
2024-05-28 9:01 ` dpdklab
2024-05-28 9:01 ` dpdklab
2024-05-28 9:03 ` dpdklab
2024-05-28 9:08 ` dpdklab
2024-05-28 10:48 ` dpdklab
2024-05-30 1:01 ` dpdklab
2024-05-30 1:01 ` dpdklab
2024-05-30 1:03 ` 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=202405280548.44S5mC3f3449370@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).