From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139541 [PATCH v1] dts: rename execution to test run
Date: Fri, 19 Apr 2024 16:28:10 +0800 [thread overview]
Message-ID: <202404190828.43J8SAnU2220175@localhost.localdomain> (raw)
In-Reply-To: <20240419085108.97519-1-juraj.linkes@pantheon.tech>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139541
_Compilation OK_
Submitter: Juraj Linkeš <juraj.linkes@pantheon.tech>
Date: Fri, 19 Apr 2024 10:51:08 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139541 --> 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-19 8:53 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240419085108.97519-1-juraj.linkes@pantheon.tech>
2024-04-19 8:28 ` qemudev [this message]
2024-04-19 8:32 ` qemudev
2024-04-19 8:51 ` checkpatch
2024-04-19 9:44 ` 0-day Robot
2024-04-19 10:18 ` |SUCCESS| pw139541 [PATCH] [v1] " dpdklab
2024-04-19 10:25 ` dpdklab
2024-04-19 10:32 ` dpdklab
2024-04-19 10:34 ` dpdklab
2024-04-19 10:35 ` dpdklab
2024-04-19 10:37 ` dpdklab
2024-04-19 10:40 ` dpdklab
2024-04-19 11:10 ` dpdklab
2024-04-19 11:12 ` dpdklab
2024-04-19 11:13 ` dpdklab
2024-04-19 11:15 ` dpdklab
2024-04-19 11:16 ` dpdklab
2024-04-19 11:18 ` dpdklab
2024-04-19 11:18 ` dpdklab
2024-04-19 11:18 ` dpdklab
2024-04-19 11:18 ` dpdklab
2024-04-19 11:20 ` dpdklab
2024-04-19 11:21 ` dpdklab
2024-04-19 11:21 ` dpdklab
2024-04-19 11:21 ` dpdklab
2024-04-19 11:22 ` dpdklab
2024-04-19 11:22 ` dpdklab
2024-04-19 11:22 ` dpdklab
2024-04-19 11:23 ` dpdklab
2024-04-19 11:24 ` dpdklab
2024-04-19 11:25 ` dpdklab
2024-04-19 11:26 ` dpdklab
2024-04-19 11:27 ` dpdklab
2024-04-19 11:28 ` dpdklab
2024-04-19 11:28 ` dpdklab
2024-04-19 11:29 ` dpdklab
2024-04-19 11:30 ` dpdklab
2024-04-19 11:30 ` dpdklab
2024-04-19 11:30 ` dpdklab
2024-04-19 11:32 ` dpdklab
2024-04-19 11:33 ` dpdklab
2024-04-19 11:33 ` dpdklab
2024-04-19 11:34 ` dpdklab
2024-04-19 11:34 ` dpdklab
2024-04-19 11:34 ` dpdklab
2024-04-19 11:34 ` dpdklab
2024-04-19 11:35 ` dpdklab
2024-04-19 11:35 ` dpdklab
2024-04-19 11:35 ` dpdklab
2024-04-19 11:36 ` dpdklab
2024-04-19 11:36 ` dpdklab
2024-04-19 11:37 ` dpdklab
2024-04-19 11:37 ` dpdklab
2024-04-19 11:39 ` dpdklab
2024-04-19 11:40 ` dpdklab
2024-04-19 11:40 ` dpdklab
2024-04-19 11:41 ` dpdklab
2024-04-19 11:42 ` dpdklab
2024-04-19 11:42 ` dpdklab
2024-04-19 11:43 ` dpdklab
2024-04-19 11:43 ` dpdklab
2024-04-19 11:44 ` dpdklab
2024-04-19 11:45 ` dpdklab
2024-04-19 11:46 ` dpdklab
2024-04-19 11:46 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:50 ` dpdklab
2024-04-19 11:56 ` dpdklab
2024-04-19 12:02 ` dpdklab
2024-04-19 12:26 ` dpdklab
2024-04-19 12:28 ` dpdklab
2024-04-19 12:30 ` dpdklab
2024-04-19 12:34 ` dpdklab
2024-04-19 12:47 ` dpdklab
2024-04-19 12:48 ` |FAILURE| " dpdklab
2024-04-19 12:54 ` |SUCCESS| " dpdklab
2024-04-19 13:02 ` |FAILURE| " dpdklab
2024-04-19 13:04 ` |SUCCESS| " dpdklab
2024-04-19 13:24 ` dpdklab
2024-04-19 13:37 ` 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=202404190828.43J8SAnU2220175@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).