From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139242-139243 [PATCH 2/2] ARM64: Cross-Compilation Support
Date: Fri, 12 Apr 2024 18:51:11 +0800 [thread overview]
Message-ID: <202404121051.43CApBk41397435@localhost.localdomain> (raw)
In-Reply-To: <20240412111317.3530529-2-sebastian.brzezinka@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139243
_Compilation OK_
Submitter: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
Date: Fri, 12 Apr 2024 13:13:16 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139242-139243 --> 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-12 11:16 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240412111317.3530529-2-sebastian.brzezinka@intel.com>
2024-04-12 10:51 ` qemudev [this message]
2024-04-12 10:55 ` qemudev
2024-04-12 11:14 ` |SUCCESS| pw139243 " checkpatch
2024-04-12 12:04 ` |FAILURE| " 0-day Robot
2024-04-12 12:05 ` |SUCCESS| pw139242-139243 [PATCH] [2/2] ARM64: Cross-Compilation Sup dpdklab
2024-04-12 12:06 ` dpdklab
2024-04-12 12:06 ` dpdklab
2024-04-12 12:07 ` dpdklab
2024-04-12 12:08 ` dpdklab
2024-04-12 12:09 ` dpdklab
2024-04-12 12:10 ` dpdklab
2024-04-12 12:11 ` dpdklab
2024-04-12 12:11 ` dpdklab
2024-04-12 12:11 ` dpdklab
2024-04-12 12:11 ` dpdklab
2024-04-12 12:12 ` dpdklab
2024-04-12 12:12 ` |FAILURE| " dpdklab
2024-04-12 12:12 ` |SUCCESS| " dpdklab
2024-04-12 12:12 ` dpdklab
2024-04-12 12:12 ` dpdklab
2024-04-12 12:13 ` |FAILURE| " dpdklab
2024-04-12 12:13 ` |SUCCESS| " dpdklab
2024-04-12 12:13 ` dpdklab
2024-04-12 12:14 ` dpdklab
2024-04-12 12:18 ` dpdklab
2024-04-12 12:18 ` dpdklab
2024-04-12 12:18 ` dpdklab
2024-04-12 12:19 ` dpdklab
2024-04-12 12:19 ` |FAILURE| " dpdklab
2024-04-12 12:19 ` dpdklab
2024-04-12 12:19 ` dpdklab
2024-04-12 12:19 ` dpdklab
2024-04-12 12:19 ` |SUCCESS| " dpdklab
2024-04-12 12:20 ` dpdklab
2024-04-12 12:20 ` dpdklab
2024-04-12 12:20 ` |FAILURE| " dpdklab
2024-04-12 12:20 ` |SUCCESS| " dpdklab
2024-04-12 12:20 ` dpdklab
2024-04-12 12:20 ` dpdklab
2024-04-12 12:20 ` |FAILURE| " dpdklab
2024-04-12 12:21 ` |SUCCESS| " dpdklab
2024-04-12 12:21 ` dpdklab
2024-04-12 12:21 ` dpdklab
2024-04-12 12:21 ` |FAILURE| " dpdklab
2024-04-12 12:21 ` |SUCCESS| " dpdklab
2024-04-12 12:22 ` dpdklab
2024-04-12 12:22 ` dpdklab
2024-04-12 12:22 ` dpdklab
2024-04-12 12:22 ` dpdklab
2024-04-12 12:25 ` dpdklab
2024-04-12 12:28 ` dpdklab
2024-04-12 12:29 ` dpdklab
2024-04-12 12:29 ` |FAILURE| " dpdklab
2024-04-12 12:29 ` |SUCCESS| " dpdklab
2024-04-12 12:29 ` dpdklab
2024-04-12 12:30 ` dpdklab
2024-04-12 12:30 ` dpdklab
2024-04-12 12:30 ` dpdklab
2024-04-12 12:31 ` dpdklab
2024-04-12 12:31 ` dpdklab
2024-04-12 12:31 ` dpdklab
2024-04-12 12:32 ` dpdklab
2024-04-12 12:32 ` dpdklab
2024-04-12 12:36 ` dpdklab
2024-04-12 12:37 ` dpdklab
2024-04-12 12:37 ` dpdklab
2024-04-12 12:39 ` dpdklab
2024-04-12 12:39 ` dpdklab
2024-04-12 12:40 ` dpdklab
2024-04-12 12:40 ` dpdklab
2024-04-12 12:41 ` dpdklab
2024-04-12 12:41 ` dpdklab
2024-04-12 12:41 ` dpdklab
2024-04-12 12:42 ` dpdklab
2024-04-12 12:42 ` dpdklab
2024-04-12 12:42 ` dpdklab
2024-04-12 12:42 ` dpdklab
2024-04-12 12:43 ` dpdklab
2024-04-12 13:01 ` dpdklab
2024-04-12 13:02 ` dpdklab
2024-04-12 13:06 ` dpdklab
2024-04-12 13:22 ` dpdklab
2024-04-12 13:29 ` |FAILURE| " dpdklab
2024-04-12 13:34 ` dpdklab
2024-04-12 13:40 ` |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=202404121051.43CApBk41397435@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).