From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139495 [PATCH v4] dts: Change hugepage runtime config to 2MB Exclusively
Date: Thu, 18 Apr 2024 23:47:08 +0800 [thread overview]
Message-ID: <202404181547.43IFl82U1772686@localhost.localdomain> (raw)
In-Reply-To: <20240418161026.2839-1-npratte@iol.unh.edu>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139495
_Compilation OK_
Submitter: Nicholas Pratte <npratte@iol.unh.edu>
Date: Thu, 18 Apr 2024 12:10:26 -0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139495 --> 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-04-18 16:12 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240418161026.2839-1-npratte@iol.unh.edu>
2024-04-18 15:47 ` qemudev [this message]
2024-04-18 15:51 ` qemudev
2024-04-18 16:11 ` checkpatch
2024-04-18 17:05 ` |SUCCESS| pw139495 [PATCH] [v4] dts: Change hugepage runtime config dpdklab
2024-04-18 17:05 ` |SUCCESS| pw139495 [PATCH v4] dts: Change hugepage runtime config to 2MB Exclusively 0-day Robot
2024-04-18 17:06 ` |SUCCESS| pw139495 [PATCH] [v4] dts: Change hugepage runtime config dpdklab
2024-04-18 17:06 ` dpdklab
2024-04-18 17:06 ` dpdklab
2024-04-18 17:07 ` dpdklab
2024-04-18 17:07 ` dpdklab
2024-04-18 17:07 ` dpdklab
2024-04-18 17:07 ` dpdklab
2024-04-18 17:07 ` dpdklab
2024-04-18 17:07 ` dpdklab
2024-04-18 17:08 ` dpdklab
2024-04-18 17:08 ` dpdklab
2024-04-18 17:08 ` dpdklab
2024-04-18 17:09 ` dpdklab
2024-04-18 17:09 ` dpdklab
2024-04-18 17:09 ` dpdklab
2024-04-18 17:09 ` dpdklab
2024-04-18 17:09 ` dpdklab
2024-04-18 17:10 ` dpdklab
2024-04-18 17:10 ` dpdklab
2024-04-18 17:10 ` dpdklab
2024-04-18 17:10 ` dpdklab
2024-04-18 17:11 ` dpdklab
2024-04-18 17:11 ` dpdklab
2024-04-18 17:11 ` dpdklab
2024-04-18 17:12 ` dpdklab
2024-04-18 17:12 ` dpdklab
2024-04-18 17:12 ` dpdklab
2024-04-18 17:13 ` dpdklab
2024-04-18 17:13 ` dpdklab
2024-04-18 17:13 ` dpdklab
2024-04-18 17:13 ` dpdklab
2024-04-18 17:14 ` dpdklab
2024-04-18 17:14 ` dpdklab
2024-04-18 17:15 ` dpdklab
2024-04-18 17:15 ` dpdklab
2024-04-18 17:15 ` dpdklab
2024-04-18 17:15 ` dpdklab
2024-04-18 17:15 ` dpdklab
2024-04-18 17:16 ` |FAILURE| " dpdklab
2024-04-18 17:16 ` |SUCCESS| " dpdklab
2024-04-18 17:16 ` dpdklab
2024-04-18 17:16 ` dpdklab
2024-04-18 17:16 ` |FAILURE| " dpdklab
2024-04-18 17:17 ` |SUCCESS| " dpdklab
2024-04-18 17:17 ` dpdklab
2024-04-18 17:17 ` dpdklab
2024-04-18 17:17 ` |FAILURE| " dpdklab
2024-04-18 17:18 ` |SUCCESS| " dpdklab
2024-04-18 17:18 ` dpdklab
2024-04-18 17:18 ` |FAILURE| " dpdklab
2024-04-18 17:18 ` |SUCCESS| " dpdklab
2024-04-18 17:19 ` |FAILURE| " dpdklab
2024-04-18 17:19 ` |SUCCESS| " dpdklab
2024-04-18 17:19 ` dpdklab
2024-04-18 17:20 ` |FAILURE| " dpdklab
2024-04-18 17:20 ` |SUCCESS| " dpdklab
2024-04-18 17:20 ` |FAILURE| " dpdklab
2024-04-18 17:21 ` |SUCCESS| " dpdklab
2024-04-18 17:21 ` dpdklab
2024-04-18 17:21 ` |FAILURE| " dpdklab
2024-04-18 17:22 ` dpdklab
2024-04-18 17:22 ` |SUCCESS| " dpdklab
2024-04-18 17:22 ` dpdklab
2024-04-18 17:23 ` |FAILURE| " dpdklab
2024-04-18 17:24 ` dpdklab
2024-04-18 17:24 ` dpdklab
2024-04-18 17:25 ` dpdklab
2024-04-18 17:25 ` dpdklab
2024-04-18 17:27 ` |SUCCESS| " dpdklab
2024-04-18 17:28 ` dpdklab
2024-04-18 17:31 ` dpdklab
2024-04-18 17:34 ` dpdklab
2024-04-18 17:38 ` |FAILURE| " dpdklab
2024-04-18 17:48 ` |SUCCESS| " dpdklab
2024-04-18 18:01 ` dpdklab
2024-04-18 18:01 ` dpdklab
2024-04-18 18:05 ` dpdklab
2024-04-18 18:09 ` dpdklab
2024-04-18 18:16 ` dpdklab
2024-04-18 18:17 ` dpdklab
2024-04-18 18:29 ` dpdklab
2024-04-18 18:33 ` dpdklab
2024-04-18 22:16 ` dpdklab
2024-04-18 22:32 ` 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=202404181547.43IFl82U1772686@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).