From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw156144 [PATCH] vduse: fix typo in struct vduse_iova_info comment
Date: Mon, 25 Aug 2025 16:11:19 +0800 [thread overview]
Message-ID: <202508250811.57P8BJ021503159@localhost.localdomain> (raw)
In-Reply-To: <20250825083229.919586-1-ashwini@wisig.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/156144
_Compilation OK_
Submitter: Ashwini Sahu <ashwini@wisig.com>
Date: Mon, 25 Aug 2025 14:02:28 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 38543d33bd47fc0ee21f59db80a8763620741879
156144 --> 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-08-25 8:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250825083229.919586-1-ashwini@wisig.com>
2025-08-25 8:11 ` qemudev [this message]
2025-08-25 8:16 ` qemudev
2025-08-25 8:30 ` checkpatch
2025-08-25 9:48 ` 0-day Robot
2025-08-25 16:42 ` |PENDING| pw156144 [PATCH] vduse: fix typo in struct vduse_iova_info dpdklab
2025-08-25 16:48 ` |SUCCESS| " dpdklab
2025-08-25 16:51 ` dpdklab
2025-08-25 16:51 ` dpdklab
2025-08-25 17:07 ` dpdklab
2025-08-25 17:20 ` |PENDING| " dpdklab
2025-08-25 18:07 ` |SUCCESS| " dpdklab
2025-08-25 18:14 ` |PENDING| " dpdklab
2025-08-25 18:16 ` dpdklab
2025-08-25 18:17 ` |FAILURE| " dpdklab
2025-08-25 18:19 ` |SUCCESS| " dpdklab
2025-08-25 19:07 ` |WARNING| " dpdklab
2025-08-25 19:46 ` dpdklab
2025-08-25 19:58 ` |SUCCESS| " dpdklab
2025-08-25 20:09 ` dpdklab
2025-08-25 20:09 ` dpdklab
2025-08-25 20:12 ` |WARNING| " dpdklab
2025-08-25 21:19 ` |SUCCESS| " dpdklab
2025-08-25 21:20 ` 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=202508250811.57P8BJ021503159@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).