automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139534-139540 [PATCH v3 7/7] dma/odm: add remaining ops
Date: Fri, 19 Apr 2024 14:21:35 +0800	[thread overview]
Message-ID: <202404190621.43J6LZ1g2159946@localhost.localdomain> (raw)
In-Reply-To: <20240419064319.149-8-anoobj@marvell.com>

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

_Compilation OK_

Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Fri, 19 Apr 2024 12:13:13 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139534-139540 --> 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-19  6:46 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240419064319.149-8-anoobj@marvell.com>
2024-04-19  6:21 ` qemudev [this message]
2024-04-19  6:26 ` qemudev
2024-04-19  6:46 ` |WARNING| pw139540 " checkpatch
2024-04-19  7:44 ` |SUCCESS| " 0-day Robot
2024-04-19 10:55 ` |SUCCESS| pw139534-139540 [PATCH] [v3,7/7] dma/odm: add remaining op dpdklab
2024-04-19 10:55 ` dpdklab
2024-04-19 11:05 ` dpdklab
2024-04-19 11:06 ` dpdklab
2024-04-19 11:15 ` dpdklab
2024-04-19 11:17 ` dpdklab
2024-04-19 11:22 ` dpdklab
2024-04-19 11:25 ` dpdklab
2024-04-19 11:25 ` dpdklab
2024-04-19 11:26 ` dpdklab
2024-04-19 11:26 ` dpdklab
2024-04-19 11:26 ` dpdklab
2024-04-19 11:27 ` dpdklab
2024-04-19 11:28 ` dpdklab
2024-04-19 11:29 ` dpdklab
2024-04-19 11:30 ` dpdklab
2024-04-19 11:30 ` dpdklab
2024-04-19 11:31 ` dpdklab
2024-04-19 11:32 ` dpdklab
2024-04-19 11:32 ` dpdklab
2024-04-19 11:34 ` dpdklab
2024-04-19 11:34 ` dpdklab
2024-04-19 11:34 ` dpdklab
2024-04-19 11:35 ` dpdklab
2024-04-19 11:36 ` dpdklab
2024-04-19 11:36 ` dpdklab
2024-04-19 11:37 ` dpdklab
2024-04-19 11:37 ` dpdklab
2024-04-19 11:37 ` dpdklab
2024-04-19 11:39 ` dpdklab
2024-04-19 11:40 ` dpdklab
2024-04-19 11:40 ` dpdklab
2024-04-19 11:41 ` dpdklab
2024-04-19 11:42 ` dpdklab
2024-04-19 11:42 ` dpdklab
2024-04-19 11:42 ` dpdklab
2024-04-19 11:43 ` dpdklab
2024-04-19 11:45 ` dpdklab
2024-04-19 11:46 ` dpdklab
2024-04-19 11:46 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:47 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:48 ` dpdklab
2024-04-19 11:49 ` dpdklab
2024-04-19 11:49 ` dpdklab
2024-04-19 11:49 ` dpdklab
2024-04-19 11:49 ` dpdklab
2024-04-19 11:50 ` dpdklab
2024-04-19 11:50 ` dpdklab
2024-04-19 11:57 ` dpdklab
2024-04-19 11:58 ` dpdklab
2024-04-19 11:58 ` dpdklab
2024-04-19 12:57 ` dpdklab
2024-04-19 13:04 ` dpdklab
2024-04-19 13:15 ` dpdklab
2024-04-19 13:17 ` dpdklab
2024-04-19 13:23 ` dpdklab
2024-04-19 13:28 ` dpdklab
2024-04-19 13:29 ` dpdklab
2024-04-19 13:33 ` dpdklab
2024-04-19 13:44 ` dpdklab
2024-04-19 13:44 ` dpdklab
2024-04-19 13:51 ` dpdklab
2024-04-19 14:26 ` 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=202404190621.43J6LZ1g2159946@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).