From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw151434-151437 [PATCH v7 4/4] lib: change find device and cmp dev name functions
Date: Thu, 13 Feb 2025 00:05:34 +0800 [thread overview]
Message-ID: <202502121605.51CG5YYF477147@localhost.localdomain> (raw)
In-Reply-To: <20250212163836.178976-4-shperetz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/151437
_Compilation OK_
Submitter: Shani Peretz <shperetz@nvidia.com>
Date: Wed, 12 Feb 2025 18:38:32 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e5176f23ae8b31437c3e5eb875c81f95bf3a9942
151434-151437 --> 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-02-12 16:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250212163836.178976-4-shperetz@nvidia.com>
2025-02-12 16:05 ` qemudev [this message]
2025-02-12 16:10 ` qemudev
2025-02-12 16:41 ` |SUCCESS| pw151437 " checkpatch
2025-02-12 17:16 ` |PENDING| pw151434-151437 [PATCH] [v7,4/4] lib: change find device a dpdklab
2025-02-12 17:20 ` dpdklab
2025-02-12 17:28 ` |SUCCESS| " dpdklab
2025-02-12 17:29 ` |PENDING| " dpdklab
2025-02-12 17:37 ` |SUCCESS| " dpdklab
2025-02-12 17:39 ` dpdklab
2025-02-12 17:39 ` |PENDING| " dpdklab
2025-02-12 17:46 ` |SUCCESS| " dpdklab
2025-02-12 17:46 ` dpdklab
2025-02-12 17:59 ` dpdklab
2025-02-12 18:07 ` |SUCCESS| pw151437 [PATCH v7 4/4] lib: change find device and cmp dev name functions 0-day Robot
2025-02-12 18:19 ` |SUCCESS| pw151434-151437 [PATCH] [v7,4/4] lib: change find device a dpdklab
2025-02-12 18:21 ` dpdklab
2025-02-12 18:39 ` dpdklab
2025-02-12 19:04 ` dpdklab
2025-02-12 19:39 ` dpdklab
2025-02-12 21:24 ` 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=202502121605.51CG5YYF477147@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).