From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw156266-156268 [RFC PATCH 3/3] app/testpmd: support link state on close ethdev API
Date: Fri, 29 Aug 2025 21:29:53 +0800 [thread overview]
Message-ID: <202508291329.57TDTrs23548804@localhost.localdomain> (raw)
In-Reply-To: <20250829140224.1748255-4-ciara.loftus@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/156268
_Compilation OK_
Submitter: Ciara Loftus <ciara.loftus@intel.com>
Date: Fri, 29 Aug 2025 14:02:22 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 6d3da1115e14765645c902116e77dd4db9288279
156266-156268 --> 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-29 14:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250829140224.1748255-4-ciara.loftus@intel.com>
2025-08-29 13:29 ` qemudev [this message]
2025-08-29 13:35 ` qemudev
2025-08-29 14:01 ` |SUCCESS| pw156268 " checkpatch
2025-08-29 14:33 ` |PENDING| pw156266-156268 [PATCH] [RFC,3/3] app/testpmd: support lin dpdklab
2025-08-29 14:35 ` |SUCCESS| " dpdklab
2025-08-29 14:36 ` |PENDING| " dpdklab
2025-08-29 14:37 ` |SUCCESS| " dpdklab
2025-08-29 14:51 ` dpdklab
2025-08-29 14:53 ` dpdklab
2025-08-29 14:54 ` dpdklab
2025-08-29 14:54 ` dpdklab
2025-08-29 15:00 ` dpdklab
2025-08-29 15:08 ` |PENDING| " dpdklab
2025-08-29 15:09 ` |SUCCESS| " dpdklab
2025-08-29 15:13 ` dpdklab
2025-08-29 15:26 ` dpdklab
2025-08-29 17:44 ` |FAILURE| pw156268 [RFC PATCH 3/3] app/testpmd: support link state on close ethdev API 0-day Robot
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=202508291329.57TDTrs23548804@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).