From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144092 [PATCH v2] dts: fix runner target in the Dockerfile
Date: Tue, 17 Sep 2024 01:47:27 +0800 [thread overview]
Message-ID: <202409161747.48GHlRdn1705784@localhost.localdomain> (raw)
In-Reply-To: <20240916181445.13997-1-jspewock@iol.unh.edu>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/144092
_Compilation OK_
Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Mon, 16 Sep 2024 14:14:45 -0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
144092 --> 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-09-16 18:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240916181445.13997-1-jspewock@iol.unh.edu>
2024-09-16 17:47 ` qemudev [this message]
2024-09-16 17:52 ` qemudev
2024-09-16 18:16 ` checkpatch
2024-09-16 19:04 ` 0-day Robot
2024-09-17 6:44 ` |SUCCESS| pw144092 [PATCH] [v2] dts: fix runner target in the Docker dpdklab
2024-09-17 7:09 ` |PENDING| " dpdklab
2024-09-17 7:22 ` |SUCCESS| " dpdklab
2024-09-17 7:23 ` dpdklab
2024-09-17 7:34 ` |PENDING| " dpdklab
2024-09-17 8:19 ` |SUCCESS| " dpdklab
2024-09-17 8:24 ` dpdklab
2024-09-17 8:24 ` dpdklab
2024-09-17 8:51 ` dpdklab
2024-09-17 9:31 ` dpdklab
2024-09-17 11:09 ` dpdklab
2024-09-17 11:38 ` dpdklab
2024-09-17 11:41 ` dpdklab
2024-09-17 12:08 ` dpdklab
2024-09-17 12:11 ` dpdklab
2024-09-17 12:26 ` dpdklab
2024-09-17 21:12 ` dpdklab
2024-09-17 21:13 ` dpdklab
2024-09-22 2:28 ` dpdklab
2024-09-22 2:46 ` 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=202409161747.48GHlRdn1705784@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).