automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw142056 [PATCH v3] net/mlx5: fix matcher object memory leak
Date: Wed, 3 Jul 2024 03:49:13 +0800	[thread overview]
Message-ID: <202407021949.462JnDhe2841244@localhost.localdomain> (raw)
In-Reply-To: <20240702201450.349991-1-mahmoudmatook.mm@gmail.com>

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

_Compilation OK_

Submitter: Mahmoud Maatuq <mahmoudmatook.mm@gmail.com>
Date: Wed,  3 Jul 2024 00:14:50 +0400
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: 1ccc76de4ddfcf2e14cec6ec2f9c27c0faacda81

142056 --> 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-07-02 20:17 UTC|newest]

Thread overview: 113+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240702201450.349991-1-mahmoudmatook.mm@gmail.com>
2024-07-02 19:49 ` qemudev [this message]
2024-07-02 19:53 ` qemudev
2024-07-02 20:15 ` checkpatch
2024-07-02 21:05 ` 0-day Robot
2024-07-02 21:18 ` |PENDING| pw142056 [PATCH] [v3] net/mlx5: fix matcher object memory dpdklab
2024-07-02 21:25 ` |SUCCESS| " dpdklab
2024-07-02 21:25 ` |PENDING| " dpdklab
2024-07-02 21:29 ` dpdklab
2024-07-02 21:32 ` |SUCCESS| " dpdklab
2024-07-02 21:39 ` dpdklab
2024-07-02 21:43 ` dpdklab
2024-07-02 21:45 ` dpdklab
2024-07-02 21:49 ` dpdklab
2024-07-02 21:54 ` dpdklab
2024-07-02 21:58 ` dpdklab
2024-07-02 22:01 ` dpdklab
2024-07-02 22:07 ` dpdklab
2024-07-02 22:08 ` dpdklab
2024-07-02 22:18 ` dpdklab
2024-07-02 22:22 ` dpdklab
2024-07-02 22:23 ` |PENDING| " dpdklab
2024-07-02 22:36 ` dpdklab
2024-07-02 22:41 ` dpdklab
2024-07-02 22:46 ` dpdklab
2024-07-02 22:47 ` dpdklab
2024-07-02 22:47 ` dpdklab
2024-07-02 22:48 ` dpdklab
2024-07-02 22:50 ` dpdklab
2024-07-02 22:53 ` dpdklab
2024-07-02 22:57 ` dpdklab
2024-07-02 22:58 ` dpdklab
2024-07-02 23:03 ` dpdklab
2024-07-02 23:12 ` dpdklab
2024-07-02 23:19 ` |SUCCESS| " dpdklab
2024-07-03  0:16 ` |PENDING| " dpdklab
2024-07-03  0:19 ` dpdklab
2024-07-03  0:21 ` |SUCCESS| " dpdklab
2024-07-03  0:22 ` dpdklab
2024-07-03  0:29 ` |PENDING| " dpdklab
2024-07-03  0:37 ` dpdklab
2024-07-03  0:40 ` dpdklab
2024-07-03  0:45 ` dpdklab
2024-07-03  0:46 ` dpdklab
2024-07-03  0:48 ` dpdklab
2024-07-03  0:56 ` dpdklab
2024-07-03  0:56 ` dpdklab
2024-07-03  0:57 ` dpdklab
2024-07-03  1:05 ` dpdklab
2024-07-03  1:08 ` dpdklab
2024-07-03  1:09 ` dpdklab
2024-07-03  1:14 ` dpdklab
2024-07-03  1:33 ` dpdklab
2024-07-03  1:59 ` dpdklab
2024-07-03  2:13 ` dpdklab
2024-07-03  2:13 ` dpdklab
2024-07-03  2:28 ` dpdklab
2024-07-03  2:31 ` dpdklab
2024-07-03  2:33 ` dpdklab
2024-07-03  2:38 ` dpdklab
2024-07-03  2:45 ` dpdklab
2024-07-03  2:48 ` dpdklab
2024-07-03  2:48 ` dpdklab
2024-07-03  2:52 ` dpdklab
2024-07-03  2:53 ` dpdklab
2024-07-03  2:54 ` dpdklab
2024-07-03  2:54 ` dpdklab
2024-07-03  2:55 ` dpdklab
2024-07-03  2:58 ` dpdklab
2024-07-03  2:59 ` dpdklab
2024-07-03  3:03 ` dpdklab
2024-07-03  3:04 ` dpdklab
2024-07-03  3:06 ` dpdklab
2024-07-03  3:10 ` dpdklab
2024-07-03  3:19 ` |SUCCESS| " dpdklab
2024-07-03  3:26 ` |PENDING| " dpdklab
2024-07-03  3:28 ` dpdklab
2024-07-03  3:32 ` dpdklab
2024-07-03  3:50 ` |SUCCESS| " dpdklab
2024-07-03  4:08 ` |PENDING| " dpdklab
2024-07-03  4:09 ` dpdklab
2024-07-03  4:14 ` dpdklab
2024-07-03  4:16 ` dpdklab
2024-07-03  4:19 ` dpdklab
2024-07-03  4:29 ` dpdklab
2024-07-03  4:32 ` dpdklab
2024-07-03  4:34 ` dpdklab
2024-07-03  4:37 ` dpdklab
2024-07-03  4:38 ` dpdklab
2024-07-03  4:41 ` dpdklab
2024-07-03  4:42 ` dpdklab
2024-07-03  4:47 ` dpdklab
2024-07-03  4:48 ` dpdklab
2024-07-03  4:51 ` dpdklab
2024-07-03  4:54 ` dpdklab
2024-07-03  4:57 ` |SUCCESS| " dpdklab
2024-07-03  5:40 ` |PENDING| " dpdklab
2024-07-03  5:46 ` dpdklab
2024-07-03  5:52 ` dpdklab
2024-07-03  5:54 ` dpdklab
2024-07-03  5:59 ` dpdklab
2024-07-03  6:07 ` dpdklab
2024-07-03  6:24 ` dpdklab
2024-07-03  6:32 ` dpdklab
2024-07-03  6:36 ` dpdklab
2024-07-03  6:44 ` dpdklab
2024-07-03  6:51 ` dpdklab
2024-07-03  6:52 ` |SUCCESS| " dpdklab
2024-07-03  6:56 ` |PENDING| " dpdklab
2024-07-03  6:59 ` dpdklab
2024-07-03  7:02 ` dpdklab
2024-07-03  7:05 ` |SUCCESS| " dpdklab
2024-07-03 16:55 ` dpdklab
2024-07-03 17:09 ` 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=202407021949.462JnDhe2841244@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).