automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw132580 [PATCH] net/mlx5: fix MPRQ stride size check
Date: Fri, 13 Oct 2023 00:16:12 +0800	[thread overview]
Message-ID: <202310121616.39CGGCK5221238@localhost.localdomain> (raw)
In-Reply-To: <20231012163433.164254-1-akozyrev@nvidia.com>

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

_Compilation OK_

Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Thu, 12 Oct 2023 19:34:33 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: 51d5d8d68a38e2e07659bab9d443e72ba7bfd03b

132580 --> 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:[~2023-10-12 16:37 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231012163433.164254-1-akozyrev@nvidia.com>
2023-10-12 16:16 ` qemudev [this message]
2023-10-12 16:20 ` qemudev
2023-10-12 16:36 ` checkpatch
2023-10-12 17:39 ` 0-day Robot
2023-10-13  2:40 dpdklab
2023-10-13  2:41 dpdklab
2023-10-13  2:45 dpdklab
2023-10-13  2:45 dpdklab
2023-10-13  2:45 dpdklab
2023-10-13  2:46 dpdklab
2023-10-13  2:46 dpdklab
2023-10-13  2:46 dpdklab
2023-10-13  2:46 dpdklab
2023-10-13  2:47 dpdklab
2023-10-13  2:47 dpdklab
2023-10-13  2:48 dpdklab
2023-10-13  2:48 dpdklab
2023-10-13  2:49 dpdklab
2023-10-13  2:49 dpdklab
2023-10-13  2:49 dpdklab
2023-10-13  2:49 dpdklab
2023-10-13  2:49 dpdklab
2023-10-13  2:50 dpdklab
2023-10-13  2:50 dpdklab
2023-10-13  2:50 dpdklab
2023-10-13  2:50 dpdklab
2023-10-13  2:51 dpdklab
2023-10-13  2:51 dpdklab
2023-10-13  2:52 dpdklab
2023-10-13  2:52 dpdklab
2023-10-13  2:52 dpdklab
2023-10-13  2:53 dpdklab
2023-10-13  2:53 dpdklab
2023-10-13  2:53 dpdklab
2023-10-13  2:53 dpdklab
2023-10-13  2:54 dpdklab
2023-10-13  2:54 dpdklab
2023-10-13  2:55 dpdklab
2023-10-13  2:58 dpdklab
2023-10-13  2:59 dpdklab
2023-10-13  3:01 dpdklab
2023-10-13  3:04 dpdklab
2023-10-13  3:04 dpdklab
2023-10-13  3:05 dpdklab
2023-10-13  3:05 dpdklab
2023-10-13  3:06 dpdklab
2023-10-13  3:29 dpdklab
2023-10-13  3:57 dpdklab
2023-10-13  4:01 dpdklab
2023-10-13  6:20 dpdklab
2023-10-13 15:19 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=202310121616.39CGGCK5221238@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).