From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw150182-150196 [PATCH v3 15/15] net/ngbe: add some ops which PF has implemented
Date: Fri, 17 Jan 2025 19:17:40 +0800 [thread overview]
Message-ID: <202501171117.50HBHeh81616685@localhost.localdomain> (raw)
In-Reply-To: <20250117114455.15864-16-zaiyuwang@trustnetic.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/150196
_Compilation OK_
Submitter: Zaiyu Wang <zaiyuwang@trustnetic.com>
Date: Fri, 17 Jan 2025 19:44:39 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 34ea86164bf17a431ec5ef78d7e51e2e9b3fd75e
150182-150196 --> 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-01-17 11:51 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250117114455.15864-16-zaiyuwang@trustnetic.com>
2025-01-17 11:17 ` qemudev [this message]
2025-01-17 11:22 ` qemudev
2025-01-17 11:49 ` |SUCCESS| pw150196 " checkpatch
2025-01-17 12:44 ` 0-day Robot
2025-01-17 13:53 ` |SUCCESS| pw150182-150196 [PATCH] [v3,15/15] net/ngbe: add some ops dpdklab
2025-01-17 14:04 ` dpdklab
2025-01-17 14:07 ` dpdklab
2025-01-17 14:11 ` dpdklab
2025-01-17 14:13 ` dpdklab
2025-01-17 14:16 ` dpdklab
2025-01-17 14:21 ` dpdklab
2025-01-17 14:45 ` dpdklab
2025-01-17 14:46 ` |PENDING| " dpdklab
2025-01-17 14:51 ` |SUCCESS| " dpdklab
2025-01-17 14:55 ` |FAILURE| " dpdklab
2025-01-17 14:57 ` dpdklab
2025-01-17 15:01 ` |PENDING| " dpdklab
2025-01-17 15:02 ` |SUCCESS| " dpdklab
2025-01-17 15:03 ` dpdklab
2025-01-17 15:06 ` dpdklab
2025-01-17 15:12 ` dpdklab
2025-01-17 15:17 ` dpdklab
2025-01-17 15:20 ` |PENDING| " dpdklab
2025-01-17 15:22 ` |SUCCESS| " dpdklab
2025-01-17 15:29 ` dpdklab
2025-01-17 15:32 ` dpdklab
2025-01-17 15:33 ` dpdklab
2025-01-17 15:37 ` dpdklab
2025-01-17 15:44 ` dpdklab
2025-01-17 15:53 ` dpdklab
2025-01-17 16:10 ` dpdklab
2025-01-17 16:10 ` dpdklab
2025-01-17 16:11 ` dpdklab
2025-01-17 16:11 ` |PENDING| " dpdklab
2025-01-17 16:13 ` |SUCCESS| " dpdklab
2025-01-17 16:19 ` dpdklab
2025-01-17 16:35 ` dpdklab
2025-01-17 16:58 ` dpdklab
2025-01-17 17:05 ` |WARNING| " dpdklab
2025-01-17 17:09 ` |SUCCESS| " dpdklab
2025-01-17 17:49 ` dpdklab
2025-01-17 18:41 ` |PENDING| " dpdklab
2025-01-17 18:43 ` |SUCCESS| " dpdklab
2025-01-17 18:51 ` |WARNING| " dpdklab
2025-01-17 19:24 ` dpdklab
2025-01-17 19:31 ` dpdklab
2025-01-17 19:49 ` |SUCCESS| " dpdklab
2025-01-17 19:58 ` dpdklab
2025-01-17 21:30 ` |WARNING| " dpdklab
2025-01-17 22:07 ` 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=202501171117.50HBHeh81616685@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).