automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw154902 [PATCH] net/mlx5: fix masked indirect age action validation
Date: Tue, 1 Jul 2025 18:07:17 +0800	[thread overview]
Message-ID: <202507011007.561A7HUA731861@localhost.localdomain> (raw)
In-Reply-To: <20250701103253.318225-1-dsosnowski@nvidia.com>

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

_Compilation OK_

Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Tue, 1 Jul 2025 12:32:53 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: 5c0c1a13c34aa57c6e18f9ba852a9b5807c58b72

154902 --> 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-07-01 10:43 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250701103253.318225-1-dsosnowski@nvidia.com>
2025-07-01 10:07 ` qemudev [this message]
2025-07-01 10:11 ` qemudev
2025-07-01 10:33 ` checkpatch
2025-07-01 11:43 ` 0-day Robot
2025-07-01 13:25 ` |SUCCESS| pw154902 [PATCH] net/mlx5: fix masked indirect age action dpdklab
2025-07-01 13:27 ` dpdklab
2025-07-01 13:35 ` dpdklab
2025-07-01 13:40 ` dpdklab
2025-07-01 14:01 ` dpdklab
2025-07-01 14:14 ` dpdklab
2025-07-01 14:14 ` dpdklab
2025-07-01 14:22 ` dpdklab
2025-07-01 14:23 ` dpdklab
2025-07-01 14:34 ` |PENDING| " dpdklab
2025-07-01 14:44 ` dpdklab
2025-07-01 14:49 ` |SUCCESS| " dpdklab
2025-07-01 14:49 ` |PENDING| " dpdklab
2025-07-01 14:59 ` |SUCCESS| " dpdklab
2025-07-01 15:50 ` dpdklab
2025-07-01 15:51 ` dpdklab
2025-07-01 16:05 ` dpdklab
2025-07-01 16:08 ` |PENDING| " dpdklab
2025-07-01 16:17 ` |SUCCESS| " dpdklab
2025-07-01 16:20 ` |PENDING| " dpdklab
2025-07-01 16:30 ` dpdklab
2025-07-01 16:45 ` dpdklab
2025-07-01 16:46 ` |SUCCESS| " dpdklab
2025-07-01 17:18 ` |PENDING| " dpdklab
2025-07-01 17:21 ` |SUCCESS| " dpdklab
2025-07-01 17:24 ` dpdklab
2025-07-01 17:27 ` dpdklab
2025-07-01 17:28 ` dpdklab
2025-07-01 17:28 ` dpdklab
2025-07-01 17:28 ` dpdklab
2025-07-01 17:30 ` dpdklab
2025-07-01 17:30 ` dpdklab
2025-07-01 18:40 ` dpdklab
2025-07-01 19:00 ` dpdklab
2025-07-01 19:00 ` dpdklab
2025-07-01 19:26 ` |WARNING| " dpdklab
2025-07-01 22:03 ` dpdklab
2025-07-01 22:03 ` dpdklab
2025-07-01 22:04 ` dpdklab
2025-07-01 22:05 ` dpdklab
2025-07-01 22:37 ` |SUCCESS| " dpdklab
2025-07-02  1:46 ` dpdklab
2025-07-02  2:21 ` 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=202507011007.561A7HUA731861@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).