automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138094-138096 [PATCH v2 3/3] net/mlx5: fix indirect action async job initialization
Date: Thu, 7 Mar 2024 18:13:37 +0800	[thread overview]
Message-ID: <202403071013.427ADbYO111046@localhost.localdomain> (raw)
In-Reply-To: <20240307101910.1135720-4-getelson@nvidia.com>

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

_Compilation OK_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thu, 7 Mar 2024 12:19:08 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: 6666628362c94a0b567a39a0177539c12c97d999

138094-138096 --> 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-03-07 10:38 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240307101910.1135720-4-getelson@nvidia.com>
2024-03-07 10:13 ` qemudev [this message]
2024-03-07 10:18 ` qemudev
2024-03-07 10:20 ` |SUCCESS| pw138096 " checkpatch
2024-03-07 11:26 ` 0-day Robot
2024-03-07 14:19 ` |SUCCESS| pw138094-138096 [PATCH] [v2,3/3] net/mlx5: fix indirect ac dpdklab
2024-03-07 14:31 ` dpdklab
2024-03-07 14:50 ` dpdklab
2024-03-07 14:53 ` dpdklab
2024-03-07 14:55 ` dpdklab
2024-03-07 14:58 ` dpdklab
2024-03-07 14:59 ` dpdklab
2024-03-07 14:59 ` dpdklab
2024-03-07 14:59 ` dpdklab
2024-03-07 15:00 ` dpdklab
2024-03-07 15:00 ` dpdklab
2024-03-07 15:00 ` dpdklab
2024-03-07 15:01 ` dpdklab
2024-03-07 15:02 ` dpdklab
2024-03-07 15:04 ` dpdklab
2024-03-07 15:22 ` dpdklab
2024-03-07 16:05 ` dpdklab
2024-03-07 16:05 ` dpdklab
2024-03-07 16:06 ` dpdklab
2024-03-07 16:17 ` dpdklab
2024-03-07 16:18 ` dpdklab
2024-03-07 16:18 ` dpdklab
2024-03-07 16:19 ` dpdklab
2024-03-07 16:20 ` dpdklab
2024-03-07 16:21 ` dpdklab
2024-03-07 16:21 ` dpdklab
2024-03-07 16:22 ` dpdklab
2024-03-07 16:26 ` dpdklab
2024-03-07 16:32 ` dpdklab
2024-03-07 16:34 ` dpdklab
2024-03-07 16:35 ` dpdklab
2024-03-07 16:35 ` dpdklab
2024-03-07 16:38 ` dpdklab
2024-03-07 16:40 ` dpdklab
2024-03-07 16:42 ` dpdklab
2024-03-07 16:45 ` dpdklab
2024-03-07 16:52 ` dpdklab
2024-03-07 16:54 ` dpdklab
2024-03-07 16:56 ` dpdklab
2024-03-07 16:56 ` dpdklab
2024-03-07 16:56 ` dpdklab
2024-03-07 16:57 ` dpdklab
2024-03-07 16:57 ` dpdklab
2024-03-07 17:00 ` dpdklab
2024-03-07 17:02 ` dpdklab
2024-03-07 17:08 ` dpdklab
2024-03-07 17:30 ` dpdklab
2024-03-07 17:32 ` dpdklab
2024-03-07 17:34 ` dpdklab
2024-03-07 17:35 ` dpdklab
2024-03-07 17:35 ` dpdklab
2024-03-07 17:36 ` dpdklab
2024-03-07 17:40 ` dpdklab
2024-03-07 17:41 ` dpdklab
2024-03-07 17:43 ` dpdklab
2024-03-07 17:43 ` dpdklab
2024-03-07 17:46 ` dpdklab
2024-03-07 17:50 ` dpdklab
2024-03-07 17:50 ` dpdklab
2024-03-07 18:04 ` dpdklab
2024-03-07 18:08 ` dpdklab
2024-03-07 18:53 ` dpdklab
2024-03-07 19:48 ` dpdklab
2024-03-07 23:22 ` dpdklab
2024-03-08  6:46 ` dpdklab
2024-03-08  7:01 ` dpdklab
2024-03-08  7:15 ` dpdklab
2024-03-08  7:16 ` dpdklab
2024-03-12  1:23 ` dpdklab
2024-03-12  1:39 ` 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=202403071013.427ADbYO111046@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).