automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw158913-158930 [PATCH v5 18/18] vfio: introduce cdev mode
Date: Wed, 19 Nov 2025 18:36:05 +0800	[thread overview]
Message-ID: <202511191036.5AJAa5lK3022715@localhost.localdomain> (raw)
In-Reply-To: <684f963686006c46a9b568b29c56494db9449148.1763550470.git.anatoly.burakov@intel.com>

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

_Compilation OK_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wed, 19 Nov 2025 11:07:59 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: ef98b88455bf4a7c8b7aa3106a761c9e9270d6a3

158913-158930 --> 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-11-19 11:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <684f963686006c46a9b568b29c56494db9449148.1763550470.git.anatoly.burakov@intel.com>
2025-11-19 10:36 ` qemudev [this message]
2025-11-19 10:40 ` qemudev
2025-11-19 11:11 ` |SUCCESS| pw158930 " checkpatch
2025-11-19 12:14 ` |FAILURE| " 0-day Robot
2025-11-19 12:52 ` |PENDING| pw158913-158930 [PATCH] [v5,18/18] vfio: introduce cdev mo dpdklab
2025-11-19 13:00 ` |SUCCESS| " dpdklab
2025-11-19 13:01 ` |FAILURE| " dpdklab
2025-11-19 13:06 ` |SUCCESS| " dpdklab
2025-11-19 13:15 ` dpdklab
2025-11-19 13:24 ` |PENDING| " dpdklab
2025-11-19 13:29 ` |SUCCESS| " dpdklab
2025-11-19 13:29 ` |FAILURE| " dpdklab
2025-11-19 13:34 ` dpdklab
2025-11-19 13:41 ` |SUCCESS| " dpdklab
2025-11-19 13:55 ` dpdklab
2025-11-19 14:15 ` dpdklab
2025-11-19 14:17 ` dpdklab
2025-11-19 14:24 ` dpdklab
2025-11-19 14:33 ` |FAILURE| " 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=202511191036.5AJAa5lK3022715@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).