automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw151008-151011 [PATCH v5 4/4] lib: change find device and cmp dev name functions
Date: Thu, 6 Feb 2025 07:43:34 +0800	[thread overview]
Message-ID: <202502052343.515NhY7a3780192@localhost.localdomain> (raw)
In-Reply-To: <20250206000838.23428-5-shperetz@nvidia.com>

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

_Compilation OK_

Submitter: Shani Peretz <shperetz@nvidia.com>
Date: Thu, 6 Feb 2025 02:08:35 +0200
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 32c18e7364e30a8e43cc7cc6709a7ce606fa285e

151008-151011 --> 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-02-06  0:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250206000838.23428-5-shperetz@nvidia.com>
2025-02-05 23:43 ` qemudev [this message]
2025-02-05 23:48 ` qemudev
2025-02-06  0:09 ` |SUCCESS| pw151011 " checkpatch
2025-02-06  1:05 ` 0-day Robot
2025-02-06  2:05 ` |SUCCESS| pw151008-151011 [PATCH] [v5,4/4] lib: change find device a dpdklab
2025-02-06  2:07 ` dpdklab
2025-02-06  2:15 ` dpdklab
2025-02-06  2:22 ` dpdklab
2025-02-06  2:25 ` dpdklab
2025-02-06  2:41 ` |PENDING| " dpdklab
2025-02-06  2:41 ` dpdklab
2025-02-06  2:44 ` |SUCCESS| " dpdklab
2025-02-06  2:46 ` dpdklab
2025-02-06  3:11 ` |PENDING| " dpdklab
2025-02-06  3:31 ` |SUCCESS| " dpdklab
2025-02-06  4:50 ` |PENDING| " 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=202502052343.515NhY7a3780192@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).