automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw141174 [PATCH 1/1] net/mlx5: show rx/tx descriptor ring limitations in rte_eth_dev_info
Date: Mon, 17 Jun 2024 01:12:48 +0800	[thread overview]
Message-ID: <202406161712.45GHCmFP1526329@localhost.localdomain> (raw)
In-Reply-To: <20240616173803.424025-2-igootorov@gmail.com>

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

_Compilation OK_

Submitter: Igor Gutorov <igootorov@gmail.com>
Date: Sun, 16 Jun 2024 20:38:03 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: c1cdfbcc339c2c951bff95854983a8773d9e5b8e

141174 --> 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-06-16 17:41 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240616173803.424025-2-igootorov@gmail.com>
2024-06-16 17:12 ` qemudev [this message]
2024-06-16 17:17 ` qemudev
2024-06-16 17:39 ` checkpatch
2024-06-16 18:27 ` |SUCCESS| pw141174 [PATCH] [1/1] net/mlx5: show rx/tx descriptor rin dpdklab
2024-06-16 18:28 ` dpdklab
2024-06-16 18:29 ` dpdklab
2024-06-16 18:29 ` dpdklab
2024-06-16 18:30 ` dpdklab
2024-06-16 18:30 ` dpdklab
2024-06-16 18:31 ` dpdklab
2024-06-16 18:32 ` dpdklab
2024-06-16 18:32 ` dpdklab
2024-06-16 18:32 ` dpdklab
2024-06-16 18:32 ` dpdklab
2024-06-16 18:33 ` dpdklab
2024-06-16 18:33 ` dpdklab
2024-06-16 18:34 ` dpdklab
2024-06-16 18:34 ` dpdklab
2024-06-16 18:34 ` dpdklab
2024-06-16 18:35 ` dpdklab
2024-06-16 18:36 ` dpdklab
2024-06-16 18:36 ` dpdklab
2024-06-16 18:37 ` dpdklab
2024-06-16 18:37 ` dpdklab
2024-06-16 18:38 ` dpdklab
2024-06-16 18:38 ` dpdklab
2024-06-16 18:39 ` dpdklab
2024-06-16 18:39 ` dpdklab
2024-06-16 18:40 ` dpdklab
2024-06-16 18:41 ` dpdklab
2024-06-16 18:42 ` dpdklab
2024-06-16 18:42 ` dpdklab
2024-06-16 18:43 ` dpdklab
2024-06-16 18:43 ` dpdklab
2024-06-16 18:43 ` dpdklab
2024-06-16 18:43 ` dpdklab
2024-06-16 18:44 ` dpdklab
2024-06-16 18:44 ` dpdklab
2024-06-16 18:44 ` |SUCCESS| pw141174 [PATCH 1/1] net/mlx5: show rx/tx descriptor ring limitations in rte_eth_dev_info 0-day Robot
2024-06-16 18:44 ` |SUCCESS| pw141174 [PATCH] [1/1] net/mlx5: show rx/tx descriptor rin dpdklab
2024-06-16 18:45 ` dpdklab
2024-06-16 18:45 ` dpdklab
2024-06-16 18:45 ` dpdklab
2024-06-16 18:45 ` dpdklab
2024-06-16 18:46 ` dpdklab
2024-06-16 18:46 ` dpdklab
2024-06-16 18:46 ` dpdklab
2024-06-16 18:47 ` dpdklab
2024-06-16 18:47 ` dpdklab
2024-06-16 18:47 ` dpdklab
2024-06-16 18:47 ` dpdklab
2024-06-16 18:47 ` dpdklab
2024-06-16 18:47 ` dpdklab
2024-06-16 18:48 ` dpdklab
2024-06-16 18:49 ` dpdklab
2024-06-16 18:49 ` dpdklab
2024-06-16 18:51 ` dpdklab
2024-06-16 18:56 ` dpdklab
2024-06-16 18:56 ` dpdklab
2024-06-16 19:00 ` dpdklab
2024-06-16 19:02 ` dpdklab
2024-06-16 19:02 ` dpdklab
2024-06-16 19:03 ` dpdklab
2024-06-16 19:03 ` dpdklab
2024-06-16 19:04 ` dpdklab
2024-06-16 19:04 ` dpdklab
2024-06-16 19:04 ` dpdklab
2024-06-16 19:05 ` dpdklab
2024-06-16 19:05 ` dpdklab
2024-06-16 19:06 ` dpdklab
2024-06-16 19:07 ` dpdklab
2024-06-16 19:08 ` dpdklab
2024-06-16 19:08 ` dpdklab
2024-06-16 19:09 ` dpdklab
2024-06-16 19:10 ` dpdklab
2024-06-16 19:11 ` dpdklab
2024-06-16 19:11 ` dpdklab
2024-06-16 19:12 ` dpdklab
2024-06-16 19:14 ` dpdklab
2024-06-16 19:14 ` dpdklab
2024-06-16 19:15 ` dpdklab
2024-06-16 19:15 ` dpdklab
2024-06-16 19:16 ` dpdklab
2024-06-16 19:18 ` dpdklab
2024-06-16 19:18 ` dpdklab
2024-06-16 19:18 ` dpdklab
2024-06-16 19:20 ` dpdklab
2024-06-16 19:20 ` dpdklab
2024-06-16 19:23 ` dpdklab
2024-06-16 19:23 ` dpdklab
2024-06-16 19:24 ` dpdklab
2024-06-16 19:26 ` dpdklab
2024-06-16 19:27 ` dpdklab
2024-06-16 19:28 ` dpdklab
2024-06-16 19:28 ` dpdklab
2024-06-16 19:29 ` dpdklab
2024-06-16 19:29 ` dpdklab
2024-06-16 19:30 ` dpdklab
2024-06-16 19:32 ` dpdklab
2024-06-16 19:32 ` dpdklab
2024-06-16 19:33 ` dpdklab
2024-06-16 19:33 ` dpdklab
2024-06-16 19:36 ` dpdklab
2024-06-16 19:40 ` dpdklab
2024-06-16 19:41 ` dpdklab
2024-06-16 19:41 ` dpdklab
2024-06-16 19:42 ` dpdklab
2024-06-16 19:43 ` dpdklab
2024-06-16 19:51 ` dpdklab
2024-06-16 19:58 ` dpdklab
2024-06-16 20:29 ` dpdklab
2024-06-16 20:32 ` dpdklab
2024-06-16 20:42 ` dpdklab
2024-06-16 22:04 ` 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=202406161712.45GHCmFP1526329@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).