From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139717 [PATCH] bus/pci: fix build with musl 1.2.4 / Alpine 3.19
Date: Mon, 29 Apr 2024 17:34:56 +0800 [thread overview]
Message-ID: <202404290934.43T9YuPA2906181@localhost.localdomain> (raw)
In-Reply-To: <20240429100059.1316414-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139717
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Mon, 29 Apr 2024 12:00:59 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139717 --> 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-29 10:02 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240429100059.1316414-1-david.marchand@redhat.com>
2024-04-29 9:34 ` qemudev [this message]
2024-04-29 9:39 ` qemudev
2024-04-29 10:58 ` |SUCCESS| pw139717 [PATCH] bus/pci: fix build with musl 1.2.4 / Alpi dpdklab
2024-04-29 10:58 ` dpdklab
2024-04-29 10:59 ` dpdklab
2024-04-29 10:59 ` dpdklab
2024-04-29 10:59 ` dpdklab
2024-04-29 11:00 ` dpdklab
2024-04-29 11:01 ` dpdklab
2024-04-29 11:01 ` dpdklab
2024-04-29 11:02 ` dpdklab
2024-04-29 11:03 ` dpdklab
2024-04-29 11:04 ` dpdklab
2024-04-29 11:04 ` |SUCCESS| pw139717 [PATCH] bus/pci: fix build with musl 1.2.4 / Alpine 3.19 0-day Robot
2024-04-29 11:04 ` |SUCCESS| pw139717 [PATCH] bus/pci: fix build with musl 1.2.4 / Alpi dpdklab
2024-04-29 11:04 ` dpdklab
2024-04-29 11:04 ` dpdklab
2024-04-29 11:05 ` dpdklab
2024-04-29 11:05 ` dpdklab
2024-04-29 11:06 ` dpdklab
2024-04-29 11:06 ` dpdklab
2024-04-29 11:07 ` dpdklab
2024-04-29 11:07 ` dpdklab
2024-04-29 11:08 ` dpdklab
2024-04-29 11:09 ` dpdklab
2024-04-29 11:10 ` dpdklab
2024-04-29 11:11 ` dpdklab
2024-04-29 11:12 ` dpdklab
2024-04-29 11:12 ` dpdklab
2024-04-29 11:13 ` dpdklab
2024-04-29 11:13 ` dpdklab
2024-04-29 11:14 ` dpdklab
2024-04-29 11:14 ` dpdklab
2024-04-29 11:14 ` dpdklab
2024-04-29 11:15 ` dpdklab
2024-04-29 11:15 ` dpdklab
2024-04-29 11:15 ` dpdklab
2024-04-29 11:15 ` dpdklab
2024-04-29 11:16 ` dpdklab
2024-04-29 11:16 ` dpdklab
2024-04-29 11:16 ` dpdklab
2024-04-29 11:16 ` dpdklab
2024-04-29 11:16 ` dpdklab
2024-04-29 11:17 ` dpdklab
2024-04-29 11:17 ` dpdklab
2024-04-29 11:17 ` dpdklab
2024-04-29 11:18 ` dpdklab
2024-04-29 11:18 ` dpdklab
2024-04-29 11:18 ` dpdklab
2024-04-29 11:18 ` dpdklab
2024-04-29 11:19 ` dpdklab
2024-04-29 11:22 ` dpdklab
2024-04-29 11:22 ` dpdklab
2024-04-29 11:23 ` dpdklab
2024-04-29 11:24 ` dpdklab
2024-04-29 11:25 ` dpdklab
2024-04-29 11:27 ` dpdklab
2024-04-29 11:27 ` dpdklab
2024-04-29 11:29 ` dpdklab
2024-04-29 11:30 ` dpdklab
2024-04-29 11:31 ` dpdklab
2024-04-29 11:32 ` dpdklab
2024-04-29 11:34 ` dpdklab
2024-04-29 11:34 ` dpdklab
2024-04-29 11:34 ` dpdklab
2024-04-29 11:34 ` dpdklab
2024-04-29 11:34 ` dpdklab
2024-04-29 11:35 ` dpdklab
2024-04-29 11:35 ` dpdklab
2024-04-29 11:35 ` dpdklab
2024-04-29 11:38 ` dpdklab
2024-04-29 11:40 ` dpdklab
2024-04-29 11:42 ` dpdklab
2024-04-29 11:43 ` dpdklab
2024-04-29 11:45 ` dpdklab
2024-04-29 11:47 ` dpdklab
2024-04-29 11:47 ` dpdklab
2024-04-29 11:50 ` dpdklab
2024-04-29 11:50 ` dpdklab
2024-04-29 11:50 ` dpdklab
2024-04-29 11:51 ` dpdklab
2024-04-29 11:51 ` dpdklab
2024-04-29 11:55 ` dpdklab
2024-04-29 11:55 ` dpdklab
2024-04-29 12:00 ` dpdklab
2024-04-29 12:00 ` dpdklab
2024-04-29 12:01 ` dpdklab
2024-04-29 12:02 ` dpdklab
2024-04-29 12:10 ` dpdklab
2024-04-29 12:11 ` dpdklab
2024-04-29 13:43 ` 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=202404290934.43T9YuPA2906181@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).