From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw156046-156048 [PATCH v4 3/3] mbuf: no need to reset all fields on reinitialized mbufs
Date: Thu, 21 Aug 2025 21:53:28 +0800 [thread overview]
Message-ID: <202508211353.57LDrSUo289655@localhost.localdomain> (raw)
In-Reply-To: <20250821142544.16211-4-mb@smartsharesystems.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/156048
_Compilation OK_
Submitter: Morten Brørup <mb@smartsharesystems.com>
Date: Thu, 21 Aug 2025 14:25:42 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 38543d33bd47fc0ee21f59db80a8763620741879
156046-156048 --> 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-21 14:30 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250821142544.16211-4-mb@smartsharesystems.com>
2025-08-21 13:53 ` qemudev [this message]
2025-08-21 13:57 ` qemudev
2025-08-21 14:25 ` |SUCCESS| pw156048 " checkpatch
2025-08-21 15:29 ` |SUCCESS| pw156046-156048 [PATCH] [v4,3/3] mbuf: no need to reset al dpdklab
2025-08-21 15:44 ` dpdklab
2025-08-21 15:44 ` |FAILURE| " dpdklab
2025-08-21 15:46 ` |WARNING| " dpdklab
2025-08-21 15:47 ` dpdklab
2025-08-21 15:47 ` dpdklab
2025-08-21 15:47 ` dpdklab
2025-08-21 15:47 ` dpdklab
2025-08-21 15:48 ` dpdklab
2025-08-21 15:52 ` |FAILURE| " dpdklab
2025-08-21 15:54 ` dpdklab
2025-08-21 15:57 ` |SUCCESS| " dpdklab
2025-08-21 15:58 ` |FAILURE| " dpdklab
2025-08-21 16:03 ` |SUCCESS| " dpdklab
2025-08-21 16:20 ` dpdklab
2025-08-21 16:23 ` dpdklab
2025-08-21 16:34 ` dpdklab
2025-08-21 16:35 ` |FAILURE| " dpdklab
2025-08-21 17:42 ` dpdklab
2025-08-21 17:45 ` dpdklab
2025-08-21 19:52 ` |SUCCESS| " dpdklab
2025-08-21 20:30 ` |FAILURE| " dpdklab
2025-08-21 20:30 ` dpdklab
2025-08-21 20:31 ` dpdklab
2025-08-21 20:41 ` |SUCCESS| " dpdklab
2025-08-21 21:15 ` dpdklab
2025-08-21 21:57 ` |FAILURE| " dpdklab
2025-08-21 21:58 ` dpdklab
2025-08-21 22:43 ` dpdklab
2025-08-21 22:45 ` dpdklab
2025-08-21 22:51 ` |WARNING| " dpdklab
2025-08-22 11:32 ` |FAILURE| " dpdklab
2025-08-22 11:32 ` dpdklab
2025-08-22 11:33 ` dpdklab
2025-08-22 15:06 ` dpdklab
2025-08-22 15:07 ` dpdklab
2025-08-22 15:08 ` dpdklab
2025-08-22 15:08 ` dpdklab
2025-08-22 15:09 ` dpdklab
2025-08-22 15:10 ` dpdklab
2025-08-22 15:12 ` dpdklab
2025-08-22 15:12 ` dpdklab
2025-08-22 15:13 ` dpdklab
2025-08-22 15:14 ` dpdklab
2025-08-22 15:15 ` dpdklab
2025-08-22 15:16 ` dpdklab
2025-08-22 15:16 ` dpdklab
2025-08-22 15:18 ` dpdklab
2025-08-22 15:19 ` |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=202508211353.57LDrSUo289655@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).