automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw149306 [PATCH] bus/fslmc: fix use after rte_free
Date: Thu, 19 Dec 2024 00:35:09 +0800	[thread overview]
Message-ID: <202412181635.4BIGZ9XF2514770@localhost.localdomain> (raw)
In-Reply-To: <20241218170530.140747-1-stephen@networkplumber.org>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/149306

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed, 18 Dec 2024 09:05:30 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 4dc4e33ffa108e945fc8a1e2bbc7819791faa61e

149306 --> 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


       reply	other threads:[~2024-12-18 17:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241218170530.140747-1-stephen@networkplumber.org>
2024-12-18 16:35 ` qemudev [this message]
2024-12-18 16:39 ` qemudev
2024-12-18 17:06 ` |WARNING| " checkpatch
2024-12-18 18:09 ` |SUCCESS| " dpdklab
2024-12-18 18:11 ` dpdklab
2024-12-18 18:12 ` |FAILURE| " dpdklab
2024-12-18 18:15 ` |SUCCESS| " dpdklab
2024-12-18 18:18 ` dpdklab
2024-12-18 18:18 ` dpdklab
2024-12-18 18:19 ` dpdklab
2024-12-18 18:20 ` dpdklab
2024-12-18 18:22 ` dpdklab
2024-12-18 18:31 ` dpdklab
2024-12-18 18:40 ` dpdklab
2024-12-18 18:43 ` 0-day Robot
2024-12-18 18:47 ` |WARNING| " dpdklab
2024-12-18 18:49 ` dpdklab
2024-12-18 18:52 ` |SUCCESS| " dpdklab
2024-12-18 19:14 ` dpdklab
2024-12-18 19:47 ` |WARNING| " dpdklab
2024-12-18 21:17 ` |SUCCESS| " dpdklab
2024-12-19  0:22 ` dpdklab
2024-12-19  3:28 ` |WARNING| " dpdklab
2024-12-19  3:59 ` 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=202412181635.4BIGZ9XF2514770@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).