From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw152383-152384 [PATCH 2/2] bus/fslmc: fix use after free
Date: Fri, 14 Mar 2025 00:49:15 +0800 [thread overview]
Message-ID: <202503131649.52DGnFRT805121@localhost.localdomain> (raw)
In-Reply-To: <20250313172307.274109-3-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/152384
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 13 Mar 2025 10:22:03 -0700
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: 5f37ee9c859f3ce08ca4364f1d8c0e70ec33ac83
152383-152384 --> 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-03-13 17:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250313172307.274109-3-stephen@networkplumber.org>
2025-03-13 16:49 ` qemudev [this message]
2025-03-13 16:53 ` qemudev
2025-03-13 17:23 ` |SUCCESS| pw152384 " checkpatch
2025-03-13 19:24 ` 0-day Robot
2025-03-13 19:24 ` |SUCCESS| pw152383-152384 [PATCH] [2/2] bus/fslmc: fix use after fre dpdklab
2025-03-13 19:31 ` dpdklab
2025-03-13 19:33 ` dpdklab
2025-03-13 19:43 ` dpdklab
2025-03-13 19:48 ` dpdklab
2025-03-13 19:53 ` dpdklab
2025-03-13 20:00 ` dpdklab
2025-03-13 20:09 ` dpdklab
2025-03-13 20:10 ` |PENDING| " dpdklab
2025-03-13 20:24 ` |SUCCESS| " dpdklab
2025-03-13 20:31 ` dpdklab
2025-03-13 20:41 ` dpdklab
2025-03-13 20:45 ` dpdklab
2025-03-13 21:19 ` dpdklab
2025-03-13 21:21 ` dpdklab
2025-03-13 21:43 ` dpdklab
2025-03-13 22:18 ` 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=202503131649.52DGnFRT805121@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).