automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120817 [PATCH] net/mlx5: add debug support for dumping all rte ports
Date: Tue, 13 Dec 2022 17:26:56 +0800	[thread overview]
Message-ID: <202212130926.2BD9QuVs1963067@localhost.localdomain> (raw)
In-Reply-To: <20221213092849.7889-1-valex@nvidia.com>

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

_Compilation OK_

Submitter: Alex Vesker <valex@nvidia.com>
Date: Tue, 13 Dec 2022 11:28:49 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: f262f16087ea6a77357a915cf4c0d10ddc7b6562

120817 --> 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:[~2022-12-13  9:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221213092849.7889-1-valex@nvidia.com>
2022-12-13  9:26 ` qemudev [this message]
2022-12-13  9:30 ` qemudev
2022-12-13  9:30 ` checkpatch
2022-12-13 10:19 ` 0-day Robot
2022-12-13 14:46 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2022-12-13 12:55 dpdklab
2022-12-13 12:55 dpdklab
2022-12-13 12:55 dpdklab
2022-12-13 12:40 dpdklab
2022-12-13 12:40 dpdklab
2022-12-13 12:40 dpdklab
2022-12-13 12:24 dpdklab
2022-12-13 12:22 dpdklab
2022-12-13 11:42 dpdklab
2022-12-13 11:24 dpdklab
2022-12-13 10:40 dpdklab
2022-12-13 10:32 dpdklab
2022-12-13 10:25 dpdklab
2022-12-13 10:21 dpdklab
2022-12-13 10:13 dpdklab
2022-12-13 10:06 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=202212130926.2BD9QuVs1963067@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).