From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140054-140055 [PATCH v2 2/2] dts: clean up config types
Date: Tue, 14 May 2024 19:10:12 +0800 [thread overview]
Message-ID: <202405141110.44EBACwg3222534@localhost.localdomain> (raw)
In-Reply-To: <20240514113446.1948050-3-luca.vizzarro@arm.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140055
_Compilation OK_
Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Tue, 14 May 2024 12:34:45 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
140054-140055 --> 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-14 11:38 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240514113446.1948050-3-luca.vizzarro@arm.com>
2024-05-14 11:10 ` qemudev [this message]
2024-05-14 11:14 ` qemudev
2024-05-14 11:36 ` |SUCCESS| pw140055 " checkpatch
2024-05-14 12:14 ` |SUCCESS| pw140054-140055 [PATCH] [v2,2/2] dts: clean up config type dpdklab
2024-05-14 12:15 ` dpdklab
2024-05-14 12:15 ` dpdklab
2024-05-14 12:15 ` dpdklab
2024-05-14 12:15 ` dpdklab
2024-05-14 12:15 ` dpdklab
2024-05-14 12:15 ` dpdklab
2024-05-14 12:16 ` dpdklab
2024-05-14 12:16 ` dpdklab
2024-05-14 12:16 ` dpdklab
2024-05-14 12:16 ` dpdklab
2024-05-14 12:16 ` dpdklab
2024-05-14 12:16 ` dpdklab
2024-05-14 12:17 ` dpdklab
2024-05-14 12:17 ` dpdklab
2024-05-14 12:17 ` dpdklab
2024-05-14 12:17 ` dpdklab
2024-05-14 12:18 ` dpdklab
2024-05-14 12:18 ` dpdklab
2024-05-14 12:18 ` dpdklab
2024-05-14 12:18 ` dpdklab
2024-05-14 12:18 ` dpdklab
2024-05-14 12:18 ` dpdklab
2024-05-14 12:18 ` dpdklab
2024-05-14 12:19 ` dpdklab
2024-05-14 12:19 ` dpdklab
2024-05-14 12:20 ` dpdklab
2024-05-14 12:20 ` dpdklab
2024-05-14 12:20 ` dpdklab
2024-05-14 12:20 ` dpdklab
2024-05-14 12:20 ` dpdklab
2024-05-14 12:20 ` dpdklab
2024-05-14 12:20 ` dpdklab
2024-05-14 12:20 ` dpdklab
2024-05-14 12:21 ` dpdklab
2024-05-14 12:21 ` dpdklab
2024-05-14 12:22 ` dpdklab
2024-05-14 12:24 ` dpdklab
2024-05-14 12:29 ` dpdklab
2024-05-14 12:29 ` dpdklab
2024-05-14 12:29 ` dpdklab
2024-05-14 12:29 ` dpdklab
2024-05-14 12:29 ` dpdklab
2024-05-14 12:30 ` dpdklab
2024-05-14 12:30 ` dpdklab
2024-05-14 12:30 ` dpdklab
2024-05-14 12:31 ` dpdklab
2024-05-14 12:32 ` dpdklab
2024-05-14 12:32 ` dpdklab
2024-05-14 12:40 ` dpdklab
2024-05-14 12:41 ` dpdklab
2024-05-14 12:44 ` |SUCCESS| pw140055 [PATCH v2 2/2] dts: clean up config types 0-day Robot
2024-05-14 12:50 ` |SUCCESS| pw140054-140055 [PATCH] [v2,2/2] dts: clean up config type dpdklab
2024-05-14 12:50 ` dpdklab
2024-05-14 12:50 ` dpdklab
2024-05-14 12:51 ` dpdklab
2024-05-14 12:51 ` dpdklab
2024-05-14 12:52 ` dpdklab
2024-05-14 12:53 ` dpdklab
2024-05-14 12:53 ` dpdklab
2024-05-14 12:55 ` dpdklab
2024-05-14 12:55 ` dpdklab
2024-05-14 12:56 ` dpdklab
2024-05-14 12:58 ` dpdklab
2024-05-14 12:58 ` dpdklab
2024-05-14 12:59 ` dpdklab
2024-05-14 12:59 ` dpdklab
2024-05-14 12:59 ` dpdklab
2024-05-14 13:00 ` dpdklab
2024-05-14 13:00 ` dpdklab
2024-05-14 13:01 ` dpdklab
2024-05-14 13:01 ` dpdklab
2024-05-14 13:02 ` dpdklab
2024-05-14 13:02 ` dpdklab
2024-05-14 13:03 ` dpdklab
2024-05-14 13:03 ` dpdklab
2024-05-14 13:05 ` dpdklab
2024-05-14 13:06 ` dpdklab
2024-05-14 13:10 ` dpdklab
2024-05-14 13:11 ` dpdklab
2024-05-14 13:15 ` dpdklab
2024-05-14 13:16 ` dpdklab
2024-05-14 13:16 ` dpdklab
2024-05-14 13:22 ` dpdklab
2024-05-14 13:33 ` dpdklab
2024-05-14 13:34 ` 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=202405141110.44EBACwg3222534@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).