From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw153011 [PATCH] rust: RFC/demo of safe API for Dpdk Eal, Eth and Rxq
Date: Thu, 17 Apr 2025 22:37:16 +0800 [thread overview]
Message-ID: <202504171437.53HEbGoF072857@localhost.localdomain> (raw)
In-Reply-To: <20250417151039.186448-1-harry.van.haaren@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/153011
_Compilation OK_
Submitter: Harry van Haaren <harry.van.haaren@intel.com>
Date: Thu, 17 Apr 2025 16:10:40 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: ca1690ebd224f148268285b15b97441ccdbdd07e
153011 --> 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:[~2025-04-17 15:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250417151039.186448-1-harry.van.haaren@intel.com>
2025-04-17 14:37 ` qemudev [this message]
2025-04-17 14:42 ` qemudev
2025-04-17 15:12 ` |WARNING| " checkpatch
2025-04-17 15:43 ` |SUCCESS| pw153011 [PATCH] rust: RFC/demo of safe API for Dpdk Eal, dpdklab
2025-04-17 15:50 ` |PENDING| " dpdklab
2025-04-17 15:50 ` |SUCCESS| " dpdklab
2025-04-17 15:51 ` dpdklab
2025-04-17 15:58 ` dpdklab
2025-04-17 15:59 ` |PENDING| " dpdklab
2025-04-17 16:00 ` dpdklab
2025-04-17 16:03 ` |SUCCESS| " dpdklab
2025-04-17 16:05 ` dpdklab
2025-04-17 16:06 ` dpdklab
2025-04-17 16:17 ` dpdklab
2025-04-17 16:30 ` dpdklab
2025-04-17 16:58 ` dpdklab
2025-04-17 17:03 ` dpdklab
2025-04-17 17:11 ` dpdklab
2025-04-17 17:26 ` dpdklab
2025-04-17 17:27 ` dpdklab
2025-04-17 17:54 ` dpdklab
2025-04-17 18:15 ` 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=202504171437.53HEbGoF072857@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).