From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw156798-156801 [PATCH 4/4] net/cpfl: add cpchnl get vport info support
Date: Mon, 22 Sep 2025 13:53:30 +0800 [thread overview]
Message-ID: <202509220553.58M5rUrS3310943@localhost.localdomain> (raw)
In-Reply-To: <20250922094819.1350709-5-praveen.shetty@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/156801
_Compilation OK_
Submitter: Shetty, Praveen <praveen.shetty@intel.com>
Date: Mon, 22 Sep 2025 11:48:16 +0200
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 4159ea62922ce41566c7bab44655ad78bee85458
156798-156801 --> 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-22 6:30 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250922094819.1350709-5-praveen.shetty@intel.com>
2025-09-22 5:53 ` qemudev [this message]
2025-09-22 6:01 ` |FAILURE| " qemudev
2025-09-22 6:18 ` |SUCCESS| pw156801 " checkpatch
2025-09-22 6:42 ` |FAILURE| pw156798-156801 [PATCH] [4/4] net/cpfl: add cpchnl get vpo dpdklab
2025-09-22 6:44 ` |SUCCESS| " dpdklab
2025-09-22 6:46 ` |FAILURE| " dpdklab
2025-09-22 6:47 ` dpdklab
2025-09-22 6:48 ` |SUCCESS| " dpdklab
2025-09-22 6:49 ` |FAILURE| " dpdklab
2025-09-22 6:53 ` |SUCCESS| " dpdklab
2025-09-22 6:54 ` |FAILURE| " dpdklab
2025-09-22 6:55 ` |FAILURE| pw156801 [PATCH 4/4] net/cpfl: add cpchnl get vport info support 0-day Robot
2025-09-22 6:56 ` |FAILURE| pw156798-156801 [PATCH] [4/4] net/cpfl: add cpchnl get vpo dpdklab
2025-09-22 6:59 ` dpdklab
2025-09-22 6:59 ` dpdklab
2025-09-22 7:02 ` |SUCCESS| " dpdklab
2025-09-22 7:03 ` |PENDING| " dpdklab
2025-09-22 7:04 ` |SUCCESS| " dpdklab
2025-09-22 7:05 ` |FAILURE| " dpdklab
2025-09-22 7:06 ` |SUCCESS| " dpdklab
2025-09-22 7:06 ` dpdklab
2025-09-22 7:07 ` |FAILURE| " dpdklab
2025-09-22 7:09 ` dpdklab
2025-09-22 7:10 ` |SUCCESS| " dpdklab
2025-09-22 7:23 ` |PENDING| " dpdklab
2025-09-22 7:24 ` |FAILURE| " dpdklab
2025-09-22 7:24 ` dpdklab
2025-09-22 7:24 ` |SUCCESS| " dpdklab
2025-09-22 7:26 ` |FAILURE| " dpdklab
2025-09-22 7:26 ` dpdklab
2025-09-22 7:27 ` dpdklab
2025-09-22 7:27 ` dpdklab
2025-09-22 7:27 ` dpdklab
2025-09-22 7:29 ` |SUCCESS| " dpdklab
2025-09-22 7:29 ` |FAILURE| " dpdklab
2025-09-22 7:29 ` dpdklab
2025-09-22 7:29 ` dpdklab
2025-09-22 7:30 ` dpdklab
2025-09-22 7:30 ` dpdklab
2025-09-22 7:30 ` dpdklab
2025-09-22 7:32 ` dpdklab
2025-09-22 7:32 ` dpdklab
2025-09-22 7:32 ` dpdklab
2025-09-22 7:33 ` dpdklab
2025-09-22 7:34 ` dpdklab
2025-09-22 7:35 ` dpdklab
2025-09-22 7:36 ` dpdklab
2025-09-22 7:36 ` dpdklab
2025-09-22 7:36 ` dpdklab
2025-09-22 7:36 ` dpdklab
2025-09-22 7:37 ` dpdklab
2025-09-22 7:37 ` dpdklab
2025-09-22 7:47 ` |WARNING| " dpdklab
2025-09-22 7:54 ` |FAILURE| " dpdklab
2025-09-22 8:20 ` |WARNING| " 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=202509220553.58M5rUrS3310943@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).