From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw156851 [PATCH] rawdev: fix device ID retrieval function prototype
Date: Wed, 24 Sep 2025 13:23:26 +0800 [thread overview]
Message-ID: <202509240523.58O5NQNC4177264@localhost.localdomain> (raw)
In-Reply-To: <20250924055654.1986682-1-nkishor@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/156851
_Compilation OK_
Submitter: Nawal Kishor <nkishor@marvell.com>
Date: Wed, 24 Sep 2025 11:26:43 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 0e03ab647d07cd985a7cac36cefff5195cc3a07d
156851 --> 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-09-24 6:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250924055654.1986682-1-nkishor@marvell.com>
2025-09-24 5:23 ` qemudev [this message]
2025-09-24 5:28 ` qemudev
2025-09-24 5:55 ` checkpatch
2025-09-24 6:21 ` |PENDING| pw156851 [PATCH] rawdev: fix device ID retrieval function dpdklab
2025-09-24 6:22 ` dpdklab
2025-09-24 6:23 ` |SUCCESS| " dpdklab
2025-09-24 6:28 ` dpdklab
2025-09-24 6:31 ` |PENDING| " dpdklab
2025-09-24 6:41 ` |SUCCESS| " dpdklab
2025-09-24 6:43 ` dpdklab
2025-09-24 6:48 ` |PENDING| " dpdklab
2025-09-24 6:59 ` |WARNING| " dpdklab
2025-09-24 7:04 ` dpdklab
2025-09-24 7:09 ` |SUCCESS| " dpdklab
2025-09-24 7:12 ` dpdklab
2025-09-24 7:12 ` dpdklab
2025-09-24 7:19 ` dpdklab
2025-09-24 7:27 ` dpdklab
2025-09-24 7:39 ` dpdklab
2025-09-24 7:53 ` |SUCCESS| pw156851 [PATCH] rawdev: fix device ID retrieval function prototype 0-day Robot
2025-09-24 7:53 ` 0-day Robot
2025-09-24 9:13 ` |SUCCESS| pw156851 [PATCH] rawdev: fix device ID retrieval function dpdklab
2025-09-24 9:52 ` 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=202509240523.58O5NQNC4177264@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).