From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140504 [PATCH v5] eal: verify mmu type for DPDK support (ppc64le)
Date: Fri, 31 May 2024 00:21:53 +0800 [thread overview]
Message-ID: <202405301621.44UGLrVg940816@localhost.localdomain> (raw)
In-Reply-To: <20240530164448.148044-1-drc@linux.ibm.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140504
_Compilation OK_
Submitter: David Christensen <drc@linux.ibm.com>
Date: Thu, 30 May 2024 12:44:47 -0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 76cef1af8bdaeaf67a5c4ca5df3f221df994dc46
140504 --> 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-30 16:50 UTC|newest]
Thread overview: 170+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240530164448.148044-1-drc@linux.ibm.com>
2024-05-30 16:21 ` qemudev [this message]
2024-05-30 16:26 ` qemudev
2024-05-30 16:46 ` |WARNING| pw140504 [PATCH v5] eal: verify mmu type for DPDK support ppc64le checkpatch
2024-05-30 17:44 ` |SUCCESS| pw140504 [PATCH v5] eal: verify mmu type for DPDK support (ppc64le) 0-day Robot
2024-05-30 18:43 ` |SUCCESS| pw140504 [PATCH] [v5] eal: verify mmu type for DPDK suppor dpdklab
2024-05-30 18:51 ` dpdklab
2024-05-30 18:51 ` dpdklab
2024-05-30 19:08 ` dpdklab
2024-05-30 19:08 ` dpdklab
2024-05-30 19:08 ` dpdklab
2024-05-30 19:08 ` dpdklab
2024-05-30 19:09 ` dpdklab
2024-05-30 19:09 ` dpdklab
2024-05-30 19:10 ` dpdklab
2024-05-30 19:16 ` dpdklab
2024-05-30 19:16 ` dpdklab
2024-05-30 19:43 ` dpdklab
2024-05-30 19:51 ` dpdklab
2024-05-30 19:51 ` dpdklab
2024-05-30 19:55 ` dpdklab
2024-05-30 20:33 ` dpdklab
2024-05-30 20:36 ` dpdklab
2024-05-30 20:36 ` dpdklab
2024-05-30 20:44 ` dpdklab
2024-05-30 20:46 ` dpdklab
2024-05-30 20:47 ` dpdklab
2024-05-30 20:48 ` dpdklab
2024-05-30 20:50 ` dpdklab
2024-05-30 20:50 ` dpdklab
2024-05-30 20:52 ` dpdklab
2024-05-30 21:02 ` dpdklab
2024-05-30 21:03 ` dpdklab
2024-05-30 21:03 ` dpdklab
2024-05-30 21:14 ` dpdklab
2024-05-30 21:15 ` dpdklab
2024-05-30 21:15 ` dpdklab
2024-05-30 21:15 ` dpdklab
2024-05-30 21:16 ` dpdklab
2024-05-30 21:17 ` dpdklab
2024-05-30 21:17 ` dpdklab
2024-05-30 21:17 ` dpdklab
2024-05-30 21:18 ` dpdklab
2024-05-30 21:18 ` dpdklab
2024-05-30 21:19 ` dpdklab
2024-05-30 21:19 ` dpdklab
2024-05-30 21:45 ` dpdklab
2024-05-30 21:45 ` dpdklab
2024-05-30 21:46 ` dpdklab
2024-05-30 21:47 ` dpdklab
2024-05-30 21:48 ` dpdklab
2024-05-30 21:48 ` dpdklab
2024-05-30 21:49 ` dpdklab
2024-05-30 21:52 ` dpdklab
2024-05-30 21:57 ` dpdklab
2024-05-30 22:01 ` dpdklab
2024-05-30 22:06 ` dpdklab
2024-05-30 22:07 ` dpdklab
2024-05-30 22:08 ` dpdklab
2024-05-30 22:08 ` dpdklab
2024-05-30 22:08 ` dpdklab
2024-05-30 22:08 ` dpdklab
2024-05-30 22:14 ` dpdklab
2024-05-30 22:15 ` dpdklab
2024-05-30 22:15 ` dpdklab
2024-05-30 22:19 ` dpdklab
2024-05-30 22:19 ` dpdklab
2024-05-30 22:20 ` dpdklab
2024-05-30 22:22 ` dpdklab
2024-05-30 22:23 ` dpdklab
2024-05-30 23:03 ` dpdklab
2024-05-30 23:15 ` dpdklab
2024-05-30 23:31 ` dpdklab
2024-05-30 23:31 ` dpdklab
2024-05-30 23:41 ` dpdklab
2024-05-31 1:14 ` dpdklab
2024-05-31 1:16 ` dpdklab
2024-05-31 23:52 ` dpdklab
2024-05-31 23:53 ` dpdklab
2024-05-31 23:54 ` dpdklab
2024-05-31 23:55 ` dpdklab
2024-05-31 23:57 ` dpdklab
2024-05-31 23:57 ` dpdklab
2024-05-31 23:57 ` dpdklab
2024-06-01 0:01 ` dpdklab
2024-06-01 0:02 ` dpdklab
2024-06-01 0:49 ` dpdklab
2024-06-01 0:50 ` dpdklab
2024-06-01 0:53 ` dpdklab
2024-06-01 0:53 ` dpdklab
2024-06-01 0:54 ` dpdklab
2024-06-01 0:56 ` dpdklab
2024-06-01 0:57 ` dpdklab
2024-06-01 1:07 ` dpdklab
2024-06-01 1:11 ` dpdklab
2024-06-01 1:15 ` dpdklab
2024-06-01 1:16 ` dpdklab
2024-06-01 1:17 ` dpdklab
2024-06-01 1:20 ` dpdklab
2024-06-01 1:20 ` dpdklab
2024-06-01 1:21 ` dpdklab
2024-06-01 1:21 ` dpdklab
2024-06-01 1:21 ` dpdklab
2024-06-01 1:21 ` dpdklab
2024-06-01 1:22 ` dpdklab
2024-06-01 1:24 ` dpdklab
2024-06-01 1:25 ` dpdklab
2024-06-01 1:25 ` dpdklab
2024-06-01 1:25 ` dpdklab
2024-06-01 1:26 ` dpdklab
2024-06-01 1:26 ` dpdklab
2024-06-01 1:28 ` dpdklab
2024-06-01 1:28 ` dpdklab
2024-06-01 1:29 ` dpdklab
2024-06-01 1:32 ` dpdklab
2024-06-01 1:34 ` dpdklab
2024-06-01 1:34 ` dpdklab
2024-06-01 1:35 ` dpdklab
2024-06-01 1:38 ` dpdklab
2024-06-01 1:38 ` dpdklab
2024-06-01 1:39 ` dpdklab
2024-06-01 1:40 ` dpdklab
2024-06-01 1:41 ` dpdklab
2024-06-01 1:41 ` dpdklab
2024-06-01 1:41 ` dpdklab
2024-06-01 1:41 ` dpdklab
2024-06-01 1:41 ` dpdklab
2024-06-01 1:42 ` dpdklab
2024-06-01 1:43 ` dpdklab
2024-06-01 1:44 ` dpdklab
2024-06-01 1:44 ` dpdklab
2024-06-01 1:45 ` dpdklab
2024-06-01 1:45 ` dpdklab
2024-06-01 1:47 ` dpdklab
2024-06-01 1:47 ` dpdklab
2024-06-01 1:47 ` dpdklab
2024-06-01 1:47 ` dpdklab
2024-06-01 1:47 ` dpdklab
2024-06-01 1:48 ` dpdklab
2024-06-01 1:48 ` dpdklab
2024-06-01 1:49 ` dpdklab
2024-06-01 1:49 ` dpdklab
2024-06-01 1:49 ` dpdklab
2024-06-01 1:49 ` dpdklab
2024-06-01 1:50 ` dpdklab
2024-06-01 1:50 ` dpdklab
2024-06-01 1:51 ` dpdklab
2024-06-01 2:00 ` dpdklab
2024-06-01 2:01 ` dpdklab
2024-06-01 2:01 ` dpdklab
2024-06-01 2:02 ` dpdklab
2024-06-01 2:02 ` dpdklab
2024-06-01 2:02 ` dpdklab
2024-06-01 2:07 ` dpdklab
2024-06-01 2:08 ` dpdklab
2024-06-01 2:16 ` dpdklab
2024-06-01 2:17 ` dpdklab
2024-06-01 2:19 ` dpdklab
2024-06-01 2:20 ` dpdklab
2024-06-01 2:20 ` dpdklab
2024-06-01 2:53 ` dpdklab
2024-06-01 3:07 ` dpdklab
2024-06-01 3:53 ` dpdklab
2024-06-01 4:07 ` dpdklab
2024-06-01 4:14 ` dpdklab
2024-06-01 4:15 ` dpdklab
2024-06-01 4:18 ` dpdklab
2024-06-01 4:48 ` dpdklab
2024-06-01 7:13 ` dpdklab
2024-06-01 8:10 ` dpdklab
2024-06-01 14:01 ` 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=202405301621.44UGLrVg940816@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).