automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw152209 [PATCH v2] net/mlx5: fix flow create failure with GENEVE options match
Date: Tue, 4 Mar 2025 15:23:15 +0800	[thread overview]
Message-ID: <202503040723.5247NFdn2642864@localhost.localdomain> (raw)
In-Reply-To: <20250304075655.110947-1-mkashani@nvidia.com>

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

_Compilation OK_

Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Tue, 4 Mar 2025 09:56:54 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: cf35973540c8bb4ca5c7d105985a65a3602e5475

152209 --> 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:[~2025-03-04  7:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250304075655.110947-1-mkashani@nvidia.com>
2025-03-04  7:23 ` qemudev [this message]
2025-03-04  7:27 ` qemudev
2025-03-04  7:58 ` |WARNING| " checkpatch
2025-03-04  8:32 ` |SUCCESS| pw152209 [PATCH] [v2] net/mlx5: fix flow create failure wi dpdklab
2025-03-04  8:42 ` dpdklab
2025-03-04  8:54 ` dpdklab
2025-03-04  9:08 ` |PENDING| " dpdklab
2025-03-04  9:21 ` dpdklab
2025-03-04  9:31 ` |SUCCESS| " dpdklab
2025-03-04 10:17 ` dpdklab
2025-03-04 10:55 ` dpdklab
2025-03-04 12:20 ` |PENDING| " dpdklab
2025-03-04 12:49 ` dpdklab
2025-03-04 13:46 ` |SUCCESS| " dpdklab
2025-03-04 13:52 ` dpdklab
2025-03-04 13:52 ` 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=202503040723.5247NFdn2642864@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).