automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw153328-153331 [PATCH 4/4] bus/pci/bsd: Fix device existence check
Date: Wed, 7 May 2025 01:07:57 +0800	[thread overview]
Message-ID: <202505061707.546H7vFd3142193@localhost.localdomain> (raw)
In-Reply-To: <20250506174046.1136711-5-jfree@FreeBSD.org>

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

_Compilation OK_

Submitter: Jake Freeland <jfree@freebsd.org>
Date: Tue,  6 May 2025 12:40:41 -0500
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 75f179ebe347b6098cf3af26d3d3b7168fe3fe24

153328-153331 --> 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-05-06 17:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250506174046.1136711-5-jfree@FreeBSD.org>
2025-05-06 17:07 ` qemudev [this message]
2025-05-06 17:12 ` qemudev
2025-05-06 17:41 ` |WARNING| pw153331 " checkpatch
2025-05-06 19:04 ` |SUCCESS| " 0-day Robot
2025-05-06 21:50 ` |SUCCESS| pw153328-153331 [PATCH] [4/4] bus/pci/bsd: Fix device exis dpdklab
2025-05-06 21:57 ` dpdklab
2025-05-06 22:02 ` dpdklab
2025-05-06 22:07 ` dpdklab
2025-05-06 22:25 ` dpdklab
2025-05-06 22:34 ` dpdklab
2025-05-06 22:38 ` dpdklab
2025-05-06 22:39 ` dpdklab
2025-05-06 22:40 ` |PENDING| " dpdklab
2025-05-06 22:44 ` |SUCCESS| " dpdklab
2025-05-06 22:48 ` dpdklab
2025-05-06 22:48 ` dpdklab
2025-05-06 22:49 ` dpdklab
2025-05-06 22:52 ` dpdklab
2025-05-06 23:01 ` dpdklab
2025-05-06 23:02 ` dpdklab
2025-05-06 23:07 ` dpdklab
2025-05-06 23:08 ` dpdklab
2025-05-06 23:13 ` dpdklab
2025-05-06 23:23 ` |PENDING| " dpdklab
2025-05-06 23:27 ` |SUCCESS| " dpdklab
2025-05-06 23:27 ` |PENDING| " dpdklab
2025-05-06 23:30 ` |SUCCESS| " dpdklab
2025-05-06 23:33 ` |PENDING| " dpdklab
2025-05-07  0:08 ` |SUCCESS| " dpdklab
2025-05-07  0:08 ` dpdklab
2025-05-07  0:13 ` dpdklab
2025-05-07  0:28 ` dpdklab
2025-05-07  0:29 ` dpdklab
2025-05-07  1:01 ` dpdklab
2025-05-07  1:04 ` dpdklab
2025-05-07  1:23 ` dpdklab
2025-05-07  2:05 ` dpdklab
2025-05-07  2:22 ` dpdklab
2025-05-07  2:49 ` dpdklab
2025-05-07  2:52 ` 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=202505061707.546H7vFd3142193@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).