automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137421-137424 [PATCH v2 4/4] net/mlx5: add support for flow table resizing
Date: Wed, 28 Feb 2024 18:04:39 +0800	[thread overview]
Message-ID: <202402281004.41SA4d58902013@localhost.localdomain> (raw)
In-Reply-To: <20240228102526.434717-5-getelson@nvidia.com>

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

_Compilation OK_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Wed, 28 Feb 2024 12:25:23 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: fba0d7ac2d84dbe0e12b4989198640e14216762b

137421-137424 --> 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-02-28 10:29 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240228102526.434717-5-getelson@nvidia.com>
2024-02-28 10:04 ` qemudev [this message]
2024-02-28 10:09 ` qemudev
2024-02-28 10:27 ` |WARNING| pw137424 " checkpatch
2024-02-28 11:23 ` |SUCCESS| pw137421-137424 [PATCH] [v2,4/4] net/mlx5: add support for dpdklab
2024-02-28 11:23 ` dpdklab
2024-02-28 11:24 ` dpdklab
2024-02-28 11:33 ` dpdklab
2024-02-28 11:39 ` dpdklab
2024-02-28 11:41 ` dpdklab
2024-02-28 11:43 ` dpdklab
2024-02-28 11:43 ` dpdklab
2024-02-28 11:44 ` dpdklab
2024-02-28 11:45 ` dpdklab
2024-02-28 11:45 ` dpdklab
2024-02-28 11:46 ` dpdklab
2024-02-28 11:46 ` dpdklab
2024-02-28 11:47 ` dpdklab
2024-02-28 11:47 ` dpdklab
2024-02-28 11:54 ` dpdklab
2024-02-28 11:58 ` dpdklab
2024-02-28 11:59 ` dpdklab
2024-02-28 11:59 ` dpdklab
2024-02-28 12:00 ` dpdklab
2024-02-28 12:01 ` dpdklab
2024-02-28 12:05 ` dpdklab
2024-02-28 12:05 ` dpdklab
2024-02-28 12:05 ` dpdklab
2024-02-28 12:06 ` dpdklab
2024-02-28 12:06 ` dpdklab
2024-02-28 12:07 ` dpdklab
2024-02-28 12:08 ` dpdklab
2024-02-28 12:08 ` dpdklab
2024-02-28 12:09 ` dpdklab
2024-02-28 12:10 ` dpdklab
2024-02-28 12:11 ` dpdklab
2024-02-28 12:11 ` dpdklab
2024-02-28 12:12 ` dpdklab
2024-02-28 12:13 ` dpdklab
2024-02-28 12:13 ` dpdklab
2024-02-28 12:13 ` dpdklab
2024-02-28 12:13 ` dpdklab
2024-02-28 12:14 ` dpdklab
2024-02-28 12:14 ` dpdklab
2024-02-28 12:14 ` dpdklab
2024-02-28 12:14 ` dpdklab
2024-02-28 12:15 ` dpdklab
2024-02-28 12:15 ` dpdklab
2024-02-28 12:16 ` dpdklab
2024-02-28 12:17 ` dpdklab
2024-02-28 12:22 ` dpdklab
2024-02-28 12:22 ` dpdklab
2024-02-28 12:23 ` dpdklab
2024-02-28 12:23 ` dpdklab
2024-02-28 12:25 ` dpdklab
2024-02-28 12:25 ` dpdklab
2024-02-28 12:25 ` dpdklab
2024-02-28 12:26 ` dpdklab
2024-02-28 12:26 ` dpdklab
2024-02-28 12:28 ` dpdklab
2024-02-28 12:53 ` dpdklab
2024-02-28 12:54 ` dpdklab
2024-02-28 13:09 ` dpdklab
2024-02-28 13:12 ` dpdklab
2024-02-28 14:54 ` dpdklab
2024-02-28 17:07 ` dpdklab
2024-02-28 18:20 ` dpdklab
2024-02-28 18:27 ` dpdklab
2024-02-29  8:36 ` dpdklab
2024-02-29 20:50 ` dpdklab
2024-02-29 20:56 ` dpdklab
2024-02-29 21:00 ` dpdklab
2024-02-29 21:03 ` dpdklab
2024-03-01 10:13 ` dpdklab
2024-03-01 10:46 ` dpdklab
2024-03-01 11: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=202402281004.41SA4d58902013@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).