automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw152060 [PATCH v3] net/mlx5: add eCPRI support
Date: Wed, 26 Feb 2025 14:43:18 +0800	[thread overview]
Message-ID: <202502260643.51Q6hIVd2539537@localhost.localdomain> (raw)
In-Reply-To: <20250226071724.12769-1-bingz@nvidia.com>

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

_Compilation OK_

Submitter: Bing Zhao <bingz@nvidia.com>
Date: Wed, 26 Feb 2025 09:17:24 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: 61fc05f1c6a079c0b25b27d1668450134a784d56

152060 --> 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-02-26  7:19 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250226071724.12769-1-bingz@nvidia.com>
2025-02-26  6:43 ` qemudev [this message]
2025-02-26  6:47 ` qemudev
2025-02-26  7:19 ` checkpatch
2025-02-26  8:04 ` 0-day Robot
2025-03-01 14:57 ` |SUCCESS| pw152060 [PATCH] [v3] " dpdklab
2025-03-01 14:59 ` dpdklab
2025-03-01 14:59 ` dpdklab
2025-03-01 15:12 ` dpdklab
2025-03-01 15:24 ` dpdklab
2025-03-01 15:33 ` dpdklab
2025-03-01 15:54 ` dpdklab
2025-03-01 16:17 ` dpdklab
2025-03-01 16:19 ` dpdklab
2025-03-01 16:20 ` dpdklab
2025-03-01 16:32 ` dpdklab
2025-03-01 16:35 ` dpdklab
2025-03-01 16:39 ` dpdklab
2025-03-01 16:43 ` dpdklab
2025-03-01 16:50 ` dpdklab
2025-03-01 18:02 ` |PENDING| " dpdklab
2025-03-01 18:10 ` |FAILURE| " dpdklab
2025-03-01 18:15 ` |PENDING| " dpdklab
2025-03-01 18:23 ` |WARNING| " dpdklab
2025-03-01 18:26 ` |SUCCESS| " dpdklab
2025-03-01 18:31 ` |FAILURE| " dpdklab
2025-03-01 18:35 ` dpdklab
2025-03-01 19:00 ` |WARNING| " dpdklab
2025-03-01 19:01 ` |FAILURE| " dpdklab
2025-03-01 19:02 ` dpdklab
2025-03-01 19:19 ` |SUCCESS| " dpdklab
2025-03-01 19:42 ` |FAILURE| " dpdklab
2025-03-01 19:42 ` dpdklab
2025-03-01 22:25 ` dpdklab
2025-03-02  2:12 ` |WARNING| " dpdklab
2025-03-02  2:25 ` dpdklab
2025-03-02  7:03 ` |FAILURE| " dpdklab
2025-03-02  7:08 ` dpdklab
2025-03-02 18:43 ` |WARNING| " dpdklab
2025-03-02 18:47 ` dpdklab
2025-03-04  0:04 ` |SUCCESS| " dpdklab
2025-03-04  0:09 ` 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=202502260643.51Q6hIVd2539537@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).