From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138226-138227 [PATCH v1 2/2] dts: Add missing docstring from XML-RPC server
Date: Wed, 13 Mar 2024 01:03:16 +0800 [thread overview]
Message-ID: <202403121703.42CH3GhZ3567357@localhost.localdomain> (raw)
In-Reply-To: <20240312172558.11844-3-jspewock@iol.unh.edu>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138227
_Compilation OK_
Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Tue, 12 Mar 2024 13:25:57 -0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: a86f381b826660e88794754c41d3aec79ce9b87c
138226-138227 --> 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-03-12 17:28 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240312172558.11844-3-jspewock@iol.unh.edu>
2024-03-12 17:03 ` qemudev [this message]
2024-03-12 17:07 ` qemudev
2024-03-12 17:27 ` |SUCCESS| pw138227 " checkpatch
2024-03-12 18:23 ` |FAILURE| " 0-day Robot
2024-03-12 20:22 ` |SUCCESS| pw138226-138227 [PATCH] [v1,2/2] dts: Add missing docstrin dpdklab
2024-03-12 20:32 ` dpdklab
2024-03-12 20:34 ` dpdklab
2024-03-12 20:36 ` dpdklab
2024-03-12 20:36 ` dpdklab
2024-03-12 20:36 ` dpdklab
2024-03-12 20:37 ` dpdklab
2024-03-12 20:38 ` dpdklab
2024-03-12 20:40 ` dpdklab
2024-03-12 20:51 ` dpdklab
2024-03-12 20:51 ` dpdklab
2024-03-12 20:53 ` dpdklab
2024-03-12 20:54 ` dpdklab
2024-03-12 21:02 ` dpdklab
2024-03-12 21:08 ` dpdklab
2024-03-12 21:09 ` dpdklab
2024-03-12 21:09 ` dpdklab
2024-03-12 21:09 ` dpdklab
2024-03-12 21:09 ` dpdklab
2024-03-12 21:11 ` dpdklab
2024-03-12 21:16 ` dpdklab
2024-03-12 21:17 ` dpdklab
2024-03-12 21:32 ` dpdklab
2024-03-12 21:42 ` dpdklab
2024-03-12 21:42 ` dpdklab
2024-03-12 21:42 ` dpdklab
2024-03-12 21:43 ` dpdklab
2024-03-12 21:47 ` dpdklab
2024-03-12 21:47 ` dpdklab
2024-03-12 21:48 ` dpdklab
2024-03-12 21:48 ` dpdklab
2024-03-12 21:48 ` dpdklab
2024-03-12 21:48 ` dpdklab
2024-03-12 21:48 ` dpdklab
2024-03-12 21:49 ` dpdklab
2024-03-12 21:49 ` dpdklab
2024-03-12 21:49 ` dpdklab
2024-03-12 21:49 ` dpdklab
2024-03-12 21:52 ` dpdklab
2024-03-12 21:52 ` dpdklab
2024-03-12 21:52 ` dpdklab
2024-03-12 21:52 ` dpdklab
2024-03-12 21:53 ` dpdklab
2024-03-12 21:53 ` dpdklab
2024-03-12 21:53 ` dpdklab
2024-03-12 21:53 ` dpdklab
2024-03-12 21:53 ` dpdklab
2024-03-12 21:53 ` dpdklab
2024-03-12 21:56 ` dpdklab
2024-03-12 21:56 ` dpdklab
2024-03-12 21:56 ` dpdklab
2024-03-12 21:56 ` dpdklab
2024-03-12 21:57 ` dpdklab
2024-03-12 21:57 ` dpdklab
2024-03-12 21:57 ` dpdklab
2024-03-12 21:59 ` dpdklab
2024-03-12 21:59 ` dpdklab
2024-03-12 21:59 ` dpdklab
2024-03-12 22:00 ` dpdklab
2024-03-12 22:00 ` dpdklab
2024-03-12 22:01 ` dpdklab
2024-03-12 22:03 ` dpdklab
2024-03-12 22:44 ` dpdklab
2024-03-12 23:16 ` dpdklab
2024-03-12 23:32 ` dpdklab
2024-03-12 23:32 ` dpdklab
2024-03-12 23:43 ` dpdklab
2024-03-12 23:47 ` dpdklab
2024-03-13 0:28 ` dpdklab
2024-03-16 11:11 ` dpdklab
2024-03-16 11:48 ` 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=202403121703.42CH3GhZ3567357@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).