From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw154197 [RFC PATCH] mempool: Fix some Coverity defects
Date: Mon, 9 Jun 2025 22:17:20 +0800 [thread overview]
Message-ID: <202506091417.559EHK7l3772799@localhost.localdomain> (raw)
In-Reply-To: <20250609144226.232625-1-mb@smartsharesystems.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/154197
_Compilation OK_
Submitter: Morten Brørup <mb@smartsharesystems.com>
Date: Mon, 9 Jun 2025 14:42:26 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 9622222ea710c4f57f04ea0dc6e640152f87bfc4
154197 --> 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-06-09 14:53 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250609144226.232625-1-mb@smartsharesystems.com>
2025-06-09 14:17 ` qemudev [this message]
2025-06-09 14:22 ` qemudev
2025-06-09 14:42 ` |WARNING| " checkpatch
2025-06-09 16:04 ` |SUCCESS| " 0-day Robot
2025-06-09 17:57 ` |SUCCESS| pw154197 [PATCH] [RFC] " dpdklab
2025-06-09 18:00 ` dpdklab
2025-06-09 18:23 ` dpdklab
2025-06-09 18:34 ` dpdklab
2025-06-09 18:41 ` dpdklab
2025-06-09 19:16 ` |PENDING| " dpdklab
2025-06-09 19:16 ` dpdklab
2025-06-09 19:58 ` |FAILURE| " dpdklab
2025-06-09 20:10 ` |WARNING| " dpdklab
2025-06-09 20:18 ` |SUCCESS| " dpdklab
2025-06-09 20:44 ` |WARNING| " dpdklab
2025-06-09 20:44 ` |FAILURE| " dpdklab
2025-06-09 20:47 ` dpdklab
2025-06-09 20:50 ` |SUCCESS| " dpdklab
2025-06-09 21:37 ` |FAILURE| " dpdklab
2025-06-09 22:17 ` dpdklab
2025-06-09 22:41 ` dpdklab
2025-06-09 22:58 ` dpdklab
2025-06-09 23:11 ` |SUCCESS| " dpdklab
2025-06-09 23:11 ` dpdklab
2025-06-09 23:12 ` dpdklab
2025-06-09 23:13 ` dpdklab
2025-06-09 23:13 ` dpdklab
2025-06-09 23:13 ` |FAILURE| " dpdklab
2025-06-09 23:13 ` |SUCCESS| " dpdklab
2025-06-09 23:14 ` dpdklab
2025-06-09 23:14 ` dpdklab
2025-06-09 23:14 ` dpdklab
2025-06-09 23:15 ` dpdklab
2025-06-09 23:15 ` dpdklab
2025-06-09 23:15 ` dpdklab
2025-06-09 23:15 ` dpdklab
2025-06-09 23:15 ` dpdklab
2025-06-09 23:15 ` dpdklab
2025-06-09 23:16 ` dpdklab
2025-06-10 0:29 ` |WARNING| " dpdklab
2025-06-10 0:29 ` dpdklab
2025-06-10 0:30 ` dpdklab
2025-06-10 0:30 ` dpdklab
2025-06-10 0:30 ` dpdklab
2025-06-10 0:31 ` dpdklab
2025-06-10 0:31 ` dpdklab
2025-06-10 0:31 ` dpdklab
2025-06-10 0:31 ` dpdklab
2025-06-10 0:31 ` dpdklab
2025-06-10 0:32 ` dpdklab
2025-06-10 0:32 ` dpdklab
2025-06-10 0:32 ` dpdklab
2025-06-10 0:32 ` dpdklab
2025-06-10 0:33 ` |PENDING| " dpdklab
2025-06-10 0:33 ` |WARNING| " dpdklab
2025-06-10 2:54 ` |SUCCESS| " dpdklab
2025-06-10 3:26 ` |WARNING| " dpdklab
2025-06-10 3:31 ` |SUCCESS| " dpdklab
2025-06-10 4:49 ` |FAILURE| " dpdklab
2025-06-10 6:33 ` dpdklab
2025-06-10 10:03 ` |SUCCESS| " dpdklab
2025-06-10 10:03 ` dpdklab
2025-06-10 20:26 ` dpdklab
2025-06-10 20:26 ` dpdklab
2025-06-10 20:26 ` 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=202506091417.559EHK7l3772799@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).