From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139802 [PATCH] eal/arm: replace RTE_BUILD_BUG on non-constant
Date: Thu, 2 May 2024 21:57:11 +0800 [thread overview]
Message-ID: <202405021357.442DvBOF250633@localhost.localdomain> (raw)
In-Reply-To: <20240502142116.63760-1-daniel.gregory@bytedance.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139802
_Compilation OK_
Submitter: Daniel Gregory <daniel.gregory@bytedance.com>
Date: Thu, 2 May 2024 15:21:16 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139802 --> 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-02 14:24 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240502142116.63760-1-daniel.gregory@bytedance.com>
2024-05-02 13:57 ` qemudev [this message]
2024-05-02 14:01 ` qemudev
2024-05-02 15:24 ` 0-day Robot
2024-05-02 22:13 ` |SUCCESS| pw139802 [PATCH] eal/arm: replace RTE_BUILD_BUG on non-con dpdklab
2024-05-02 22:14 ` dpdklab
2024-05-02 22:15 ` dpdklab
2024-05-02 22:20 ` dpdklab
2024-05-02 22:21 ` dpdklab
2024-05-02 22:21 ` dpdklab
2024-05-02 22:22 ` dpdklab
2024-05-02 22:22 ` dpdklab
2024-05-02 22:22 ` dpdklab
2024-05-02 22:23 ` dpdklab
2024-05-02 22:23 ` dpdklab
2024-05-02 22:24 ` dpdklab
2024-05-02 22:24 ` dpdklab
2024-05-02 22:24 ` dpdklab
2024-05-02 22:25 ` dpdklab
2024-05-02 22:25 ` dpdklab
2024-05-02 22:26 ` dpdklab
2024-05-02 22:26 ` dpdklab
2024-05-02 22:26 ` dpdklab
2024-05-02 22:27 ` dpdklab
2024-05-02 22:27 ` dpdklab
2024-05-02 22:28 ` dpdklab
2024-05-02 22:29 ` dpdklab
2024-05-02 22:29 ` dpdklab
2024-05-02 22:30 ` dpdklab
2024-05-02 22:30 ` dpdklab
2024-05-02 22:31 ` dpdklab
2024-05-02 22:31 ` dpdklab
2024-05-02 22:31 ` dpdklab
2024-05-02 22:32 ` dpdklab
2024-05-02 22:32 ` dpdklab
2024-05-02 22:32 ` dpdklab
2024-05-02 22:32 ` dpdklab
2024-05-02 22:33 ` dpdklab
2024-05-02 22:33 ` dpdklab
2024-05-02 22:33 ` dpdklab
2024-05-02 22:33 ` dpdklab
2024-05-02 22:34 ` dpdklab
2024-05-02 22:34 ` dpdklab
2024-05-02 22:34 ` dpdklab
2024-05-02 22:34 ` dpdklab
2024-05-02 22:35 ` dpdklab
2024-05-02 22:35 ` dpdklab
2024-05-02 22:35 ` dpdklab
2024-05-02 22:37 ` dpdklab
2024-05-02 22:41 ` dpdklab
2024-05-02 22:41 ` dpdklab
2024-05-02 22:44 ` dpdklab
2024-05-02 22:57 ` dpdklab
2024-05-02 22:59 ` dpdklab
2024-05-02 22:59 ` dpdklab
2024-05-02 22:59 ` dpdklab
2024-05-02 22:59 ` dpdklab
2024-05-02 23:00 ` dpdklab
2024-05-02 23:01 ` dpdklab
2024-05-02 23:02 ` dpdklab
2024-05-02 23:02 ` dpdklab
2024-05-02 23:03 ` dpdklab
2024-05-02 23:03 ` dpdklab
2024-05-02 23:04 ` dpdklab
2024-05-02 23:05 ` dpdklab
2024-05-02 23:09 ` dpdklab
2024-05-02 23:12 ` dpdklab
2024-05-02 23:19 ` dpdklab
2024-05-02 23:20 ` dpdklab
2024-05-02 23:26 ` dpdklab
2024-05-02 23:33 ` dpdklab
2024-05-02 23:34 ` dpdklab
2024-05-02 23:35 ` dpdklab
2024-05-02 23:36 ` dpdklab
2024-05-02 23:45 ` dpdklab
2024-05-02 23:58 ` dpdklab
2024-05-03 0:06 ` dpdklab
2024-05-03 0:09 ` dpdklab
2024-05-03 0:45 ` dpdklab
2024-05-03 0:59 ` dpdklab
2024-05-03 1:02 ` dpdklab
2024-05-03 2:00 ` dpdklab
2024-05-03 2:14 ` dpdklab
2024-05-03 8:21 ` |WARNING| pw139802 [PATCH] eal/arm: replace RTE_BUILD_BUG on non-constant checkpatch
2024-05-03 9:50 ` checkpatch
2024-05-03 9:57 ` checkpatch
2024-05-03 16:01 ` |SUCCESS| pw139802 [PATCH] eal/arm: replace RTE_BUILD_BUG on non-con dpdklab
2024-05-04 23:34 ` dpdklab
2024-05-04 23:38 ` dpdklab
2024-05-04 23:42 ` dpdklab
2024-05-04 23:46 ` dpdklab
2024-05-05 0:05 ` dpdklab
2024-05-06 9:27 ` 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=202405021357.442DvBOF250633@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).