automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121839 [PATCH] net/mlx5/hws: fix memory leak on general pool db init
Date: Thu, 12 Jan 2023 03:42:06 +0800	[thread overview]
Message-ID: <202301111942.30BJg6pI2562105@localhost.localdomain> (raw)
In-Reply-To: <20230111194903.27180-1-valex@nvidia.com>

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

_Compilation OK_

Submitter: Alex Vesker <valex@nvidia.com>
Date: Wed, 11 Jan 2023 21:49:03 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: c1d039ed185bd6c8bb0499b5c357eb70e3f15fe3

121839 --> 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:[~2023-01-11 19:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230111194903.27180-1-valex@nvidia.com>
2023-01-11 19:42 ` qemudev [this message]
2023-01-11 19:46 ` qemudev
2023-01-11 19:50 ` checkpatch
2023-01-11 20:59 ` 0-day Robot
2023-01-11 20:36 dpdklab
2023-01-11 20:36 dpdklab
2023-01-11 20:41 dpdklab
2023-01-11 20:43 dpdklab
2023-01-11 20:51 dpdklab
2023-01-11 20:55 dpdklab
2023-01-11 21:02 dpdklab
2023-01-11 21:11 dpdklab
2023-01-11 22:16 dpdklab
2023-01-12  1:07 dpdklab
2023-01-12  1:19 dpdklab
2023-01-12  1:56 dpdklab
2023-01-12  1:56 dpdklab
2023-01-12  1:56 dpdklab
2023-01-12  1:56 dpdklab
2023-01-12  1:56 dpdklab
2023-01-12  2:04 dpdklab
2023-01-12  2:05 dpdklab
2023-01-12  2:05 dpdklab
2023-01-12  2:05 dpdklab
2023-01-12  3:27 dpdklab
2023-01-12  3:45 dpdklab
2023-01-12  4:23 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=202301111942.30BJg6pI2562105@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).