From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw159172 [PATCH] eal/arm: include rte_config.h upfront to fix ARM arch header selection
Date: Fri, 5 Dec 2025 15:09:25 +0800 [thread overview]
Message-ID: <202512050709.5B579Put279472@localhost.localdomain> (raw)
In-Reply-To: <tencent_0AAA93B91277A304E5303277E262EB7FC408@qq.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/159172
_Compilation OK_
Submitter: luyan <973788536@qq.com>
Date: Tue, 2 Dec 2025 16:08:49 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 80b3e9cad7599ce01f94cd6f8f966401a77e29c1
159172 --> 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-12-05 7:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_0AAA93B91277A304E5303277E262EB7FC408@qq.com>
2025-12-05 7:09 ` qemudev [this message]
2025-12-05 7:14 ` qemudev
2025-12-05 7:42 ` |WARNING| " checkpatch
2025-12-05 8:27 ` |PENDING| pw159172 [PATCH] eal/arm: include rte_config.h upfront to dpdklab
2025-12-05 8:35 ` |SUCCESS| " dpdklab
2025-12-05 8:42 ` dpdklab
2025-12-05 9:04 ` dpdklab
2025-12-05 9:09 ` dpdklab
2025-12-05 9:39 ` |PENDING| " dpdklab
2025-12-05 9:51 ` dpdklab
2025-12-05 10:08 ` |SUCCESS| " dpdklab
2025-12-05 10:10 ` dpdklab
2025-12-05 12:23 ` dpdklab
2025-12-05 12:24 ` dpdklab
2025-12-05 12:34 ` dpdklab
2025-12-05 13:09 ` dpdklab
2025-12-05 13:21 ` dpdklab
2025-12-05 13:31 ` dpdklab
2025-12-05 17:31 ` dpdklab
2025-12-05 17:48 ` dpdklab
2025-12-05 18:27 ` dpdklab
2025-12-05 22:53 ` dpdklab
2025-12-05 23:14 ` dpdklab
2025-12-06 4:13 ` dpdklab
2025-12-06 4:42 ` dpdklab
2025-12-06 5:22 ` |PENDING| " dpdklab
2025-12-06 7:14 ` |SUCCESS| " 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=202512050709.5B579Put279472@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).