From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw152462-152475 [PATCH v5 14/14] net/zxdh: fix debugging errors
Date: Wed, 19 Mar 2025 16:54:33 +0800 [thread overview]
Message-ID: <202503190854.52J8sX9N3114307@localhost.localdomain> (raw)
In-Reply-To: <20250319085808.1912523-15-chen.bingbin@zte.com.cn>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/152475
_Compilation OK_
Submitter: Bingbin Chen <chen.bingbin@zte.com.cn>
Date: Wed, 19 Mar 2025 16:57:55 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 9694dcd7d1abe20a6a838b80a6309137e02c3789
152462-152475 --> 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:[~2025-03-19 9:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250319085808.1912523-15-chen.bingbin@zte.com.cn>
2025-03-19 8:54 ` qemudev [this message]
2025-03-19 8:59 ` |FAILURE| " qemudev
2025-03-19 9:19 ` |WARNING| pw152475 " checkpatch
2025-03-19 10:04 ` |SUCCESS| " 0-day Robot
2025-03-19 18:45 ` |SUCCESS| pw152462-152475 [PATCH] [v5,14/14] net/zxdh: fix debugging dpdklab
2025-03-19 18:46 ` dpdklab
2025-03-19 18:50 ` |PENDING| " dpdklab
2025-03-19 18:55 ` |SUCCESS| " dpdklab
2025-03-19 18:58 ` dpdklab
2025-03-19 18:59 ` |PENDING| " dpdklab
2025-03-19 18:59 ` |SUCCESS| " dpdklab
2025-03-19 19:02 ` dpdklab
2025-03-19 19:08 ` dpdklab
2025-03-19 19:14 ` dpdklab
2025-03-19 19:15 ` |PENDING| " dpdklab
2025-03-19 19:20 ` |SUCCESS| " dpdklab
2025-03-19 19:21 ` dpdklab
2025-03-19 19:34 ` dpdklab
2025-03-19 20:09 ` dpdklab
2025-03-19 20:14 ` 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=202503190854.52J8sX9N3114307@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).