From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw149216 [PATCH v1] dts: bug fixes for paramiko timeout and buffered_pipe issues
Date: Fri, 13 Dec 2024 03:13:08 +0800 [thread overview]
Message-ID: <202412121913.4BCJD8743627015@localhost.localdomain> (raw)
In-Reply-To: <20241212193902.31789-1-npratte@iol.unh.edu>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/149216
_Compilation OK_
Submitter: Nicholas Pratte <npratte@iol.unh.edu>
Date: Thu, 12 Dec 2024 14:39:02 -0500
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7df61db6c387703a36306c1aea92225921e2eeb2
149216 --> 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-12-12 19:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241212193902.31789-1-npratte@iol.unh.edu>
2024-12-12 19:13 ` qemudev [this message]
2024-12-12 19:17 ` qemudev
2024-12-12 19:40 ` checkpatch
2024-12-12 20:43 ` 0-day Robot
2024-12-14 13:50 ` |SUCCESS| pw149216 [PATCH] [v1] dts: bug fixes for paramiko timeout dpdklab
2024-12-14 13:51 ` dpdklab
2024-12-14 13:54 ` dpdklab
2024-12-14 13:58 ` dpdklab
2024-12-14 14:01 ` dpdklab
2024-12-14 14:03 ` dpdklab
2024-12-14 15:01 ` dpdklab
2024-12-14 16:17 ` dpdklab
2024-12-14 16:35 ` |WARNING| " dpdklab
2024-12-14 17:07 ` dpdklab
2024-12-14 17:08 ` |SUCCESS| " dpdklab
2024-12-14 17:48 ` dpdklab
2024-12-14 17:53 ` dpdklab
2024-12-14 18:18 ` dpdklab
2024-12-14 23:12 ` dpdklab
2024-12-15 0:22 ` dpdklab
2024-12-15 1:35 ` |WARNING| " dpdklab
2024-12-15 1:37 ` dpdklab
2024-12-16 23:42 ` dpdklab
2025-01-07 17:38 ` dpdklab
2025-01-07 18:42 ` dpdklab
2025-01-07 18:44 ` dpdklab
2025-01-13 20:07 ` |PENDING| " dpdklab
2025-01-13 21:33 ` |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=202412121913.4BCJD8743627015@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).