From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw158291 [PATCH v2] net/mlx5: fix external Rx and Tx queues access
Date: Thu, 30 Oct 2025 15:07:22 +0800	[thread overview]
Message-ID: <202510300707.59U77M823382936@localhost.localdomain> (raw)
In-Reply-To: <20251030073922.205190-1-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/158291
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thu, 30 Oct 2025 09:39:22 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: 39b54f2dcf44ad1f91eabc7080cd5dea763607fd
158291 --> 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
next      parent reply	other threads:[~2025-10-30  7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251030073922.205190-1-getelson@nvidia.com>
2025-10-30  7:07 ` qemudev [this message]
2025-10-30  7:12 ` qemudev
2025-10-30  7:41 ` |WARNING| " checkpatch
2025-10-30  8:39 ` |SUCCESS| " 0-day Robot
2025-10-30  8:39 ` 0-day Robot
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=202510300707.59U77M823382936@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).