automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139435 [PATCH] usertools/devbind: add ODM DMA device
Date: Wed, 17 Apr 2024 14:53:07 +0800	[thread overview]
Message-ID: <202404170653.43H6r7YM3344450@localhost.localdomain> (raw)
In-Reply-To: <20240417071109.104-1-anoobj@marvell.com>

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

_Compilation OK_

Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Wed, 17 Apr 2024 12:41:09 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139435 --> 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:[~2024-04-17  7:18 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240417071109.104-1-anoobj@marvell.com>
2024-04-17  6:53 ` qemudev [this message]
2024-04-17  6:57 ` qemudev
2024-04-17  7:12 ` checkpatch
2024-04-17  8:04 ` 0-day Robot
2024-04-17 10:52 ` dpdklab
2024-04-17 10:53 ` dpdklab
2024-04-17 11:04 ` dpdklab
2024-04-17 11:04 ` dpdklab
2024-04-17 11:05 ` dpdklab
2024-04-17 11:07 ` dpdklab
2024-04-17 11:08 ` dpdklab
2024-04-17 11:09 ` dpdklab
2024-04-17 11:09 ` dpdklab
2024-04-17 11:10 ` dpdklab
2024-04-17 11:10 ` dpdklab
2024-04-17 11:11 ` dpdklab
2024-04-17 11:12 ` dpdklab
2024-04-17 11:12 ` dpdklab
2024-04-17 11:13 ` dpdklab
2024-04-17 11:13 ` dpdklab
2024-04-17 11:14 ` dpdklab
2024-04-17 11:14 ` dpdklab
2024-04-17 11:15 ` dpdklab
2024-04-17 11:16 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:17 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:18 ` dpdklab
2024-04-17 11:46 ` dpdklab
2024-04-17 11:46 ` dpdklab
2024-04-17 11:50 ` dpdklab
2024-04-17 11:51 ` dpdklab
2024-04-17 11:51 ` dpdklab
2024-04-17 11:53 ` dpdklab
2024-04-17 11:54 ` dpdklab
2024-04-17 11:57 ` dpdklab
2024-04-17 11:58 ` dpdklab
2024-04-17 11:58 ` dpdklab
2024-04-17 11:59 ` dpdklab
2024-04-17 12:02 ` dpdklab
2024-04-17 12:02 ` dpdklab
2024-04-17 12:03 ` dpdklab
2024-04-17 12:03 ` dpdklab
2024-04-17 12:05 ` dpdklab
2024-04-17 12:05 ` dpdklab
2024-04-17 12:06 ` dpdklab
2024-04-17 12:07 ` dpdklab
2024-04-17 12:07 ` dpdklab
2024-04-17 12:08 ` dpdklab
2024-04-17 12:08 ` dpdklab
2024-04-17 12:10 ` dpdklab
2024-04-17 12:10 ` dpdklab
2024-04-17 12:10 ` dpdklab
2024-04-17 12:10 ` dpdklab
2024-04-17 12:11 ` dpdklab
2024-04-17 12:11 ` dpdklab
2024-04-17 12:12 ` dpdklab
2024-04-17 12:14 ` dpdklab
2024-04-17 12:14 ` dpdklab
2024-04-17 12:15 ` dpdklab
2024-04-17 12:16 ` dpdklab
2024-04-17 12:16 ` dpdklab
2024-04-17 12:16 ` dpdklab
2024-04-17 12:18 ` dpdklab
2024-04-17 12:18 ` dpdklab
2024-04-17 12:19 ` dpdklab
2024-04-17 12:19 ` dpdklab
2024-04-17 12:20 ` dpdklab
2024-04-17 12:20 ` dpdklab
2024-04-17 12:20 ` dpdklab
2024-04-17 12:22 ` dpdklab
2024-04-17 12:22 ` dpdklab
2024-04-17 12:27 ` dpdklab
2024-04-17 12:30 ` dpdklab
2024-04-17 12:30 ` dpdklab
2024-04-17 12:31 ` dpdklab
2024-04-17 12:33 ` dpdklab
2024-04-17 12:33 ` dpdklab
2024-04-17 12:34 ` dpdklab
2024-04-17 12:36 ` dpdklab
2024-04-17 12:39 ` dpdklab
2024-04-17 12:41 ` dpdklab
2024-04-17 12:44 ` dpdklab
2024-04-17 12:49 ` dpdklab
2024-04-17 13:04 ` dpdklab
2024-04-17 13:08 ` dpdklab
2024-04-17 13:10 ` dpdklab
2024-04-17 13:12 ` dpdklab
2024-04-17 13:12 ` dpdklab
2024-04-17 14:29 ` dpdklab
2024-04-17 14:59 ` 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=202404170653.43H6r7YM3344450@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).