From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw154788 [PATCH] build: error out when missing elftools python module
Date: Fri, 27 Jun 2025 22:56:04 +0800 [thread overview]
Message-ID: <202506271456.55REu4NY3382819@localhost.localdomain> (raw)
In-Reply-To: <20250627152759.145084-1-bruce.richardson@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/154788
_Compilation OK_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Fri, 27 Jun 2025 15:27:59 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 2c6f1f0a847898732c18c8b37821850f1b48aa9d
154788 --> 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-06-27 15:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250627152759.145084-1-bruce.richardson@intel.com>
2025-06-27 14:56 ` qemudev [this message]
2025-06-27 15:00 ` qemudev
2025-06-27 15:28 ` checkpatch
2025-06-27 17:05 ` 0-day Robot
2025-06-27 17:07 ` |SUCCESS| pw154788 [PATCH] build: error out when missing elftools py dpdklab
2025-06-27 17:10 ` dpdklab
2025-06-27 17:18 ` dpdklab
2025-06-27 17:27 ` dpdklab
2025-06-27 17:41 ` |PENDING| " dpdklab
2025-06-27 17:46 ` dpdklab
2025-06-27 17:54 ` |SUCCESS| " dpdklab
2025-06-27 18:04 ` |PENDING| " dpdklab
2025-06-27 18:17 ` dpdklab
2025-06-27 19:20 ` |SUCCESS| " dpdklab
2025-06-27 19:26 ` dpdklab
2025-06-27 21:02 ` dpdklab
2025-06-27 21:11 ` dpdklab
2025-06-27 22:32 ` dpdklab
2025-06-27 22:40 ` |WARNING| " dpdklab
2025-06-27 22:53 ` |SUCCESS| " dpdklab
2025-06-27 22:58 ` |WARNING| " 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=202506271456.55REu4NY3382819@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).