automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138054 [PATCH v3] app/eventdev: support DMA adapter test
Date: Thu, 7 Mar 2024 02:47:07 +0800	[thread overview]
Message-ID: <202403061847.426Il7pi3359473@localhost.localdomain> (raw)
In-Reply-To: <20240306190539.1941756-1-amitprakashs@marvell.com>

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

_Compilation OK_

Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Thu, 7 Mar 2024 00:35:39 +0530
DPDK git baseline: Repo:dpdk-next-eventdev
  Branch: for-main
  CommitID: f51828c00c2c65786d4e2935b4295a524af1f217

138054 --> 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-03-06 19:12 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240306190539.1941756-1-amitprakashs@marvell.com>
2024-03-06 18:47 ` qemudev [this message]
2024-03-06 18:51 ` qemudev
2024-03-06 19:06 ` checkpatch
2024-03-06 19:47 ` |SUCCESS| pw138054 [PATCH] [v3] app/eventdev: support DMA adapter te dpdklab
2024-03-06 19:49 ` dpdklab
2024-03-06 19:52 ` dpdklab
2024-03-06 19:53 ` dpdklab
2024-03-06 19:54 ` dpdklab
2024-03-06 20:02 ` dpdklab
2024-03-06 20:03 ` dpdklab
2024-03-06 20:04 ` dpdklab
2024-03-06 20:04 ` dpdklab
2024-03-06 20:04 ` dpdklab
2024-03-06 20:04 ` |SUCCESS| pw138054 [PATCH v3] app/eventdev: support DMA adapter test 0-day Robot
2024-03-06 20:05 ` |SUCCESS| pw138054 [PATCH] [v3] app/eventdev: support DMA adapter te dpdklab
2024-03-06 20:06 ` dpdklab
2024-03-06 20:06 ` dpdklab
2024-03-06 20:06 ` dpdklab
2024-03-06 20:07 ` dpdklab
2024-03-06 20:08 ` dpdklab
2024-03-06 20:08 ` dpdklab
2024-03-06 20:08 ` dpdklab
2024-03-06 20:09 ` dpdklab
2024-03-06 20:09 ` dpdklab
2024-03-06 20:09 ` dpdklab
2024-03-06 20:13 ` dpdklab
2024-03-06 20:15 ` dpdklab
2024-03-06 20:16 ` dpdklab
2024-03-06 20:22 ` dpdklab
2024-03-06 20:24 ` dpdklab
2024-03-06 20:25 ` dpdklab
2024-03-06 20:30 ` dpdklab
2024-03-06 20:32 ` dpdklab
2024-03-06 20:35 ` dpdklab
2024-03-06 20:37 ` dpdklab
2024-03-06 20:46 ` dpdklab
2024-03-06 20:52 ` dpdklab
2024-03-06 21:05 ` dpdklab
2024-03-06 21:08 ` dpdklab
2024-03-06 21:08 ` dpdklab
2024-03-06 21:10 ` dpdklab
2024-03-06 21:11 ` dpdklab
2024-03-06 21:11 ` dpdklab
2024-03-06 21:13 ` dpdklab
2024-03-06 21:13 ` dpdklab
2024-03-06 21:13 ` dpdklab
2024-03-06 21:14 ` dpdklab
2024-03-06 21:16 ` dpdklab
2024-03-06 21:19 ` dpdklab
2024-03-06 21:20 ` dpdklab
2024-03-06 21:24 ` dpdklab
2024-03-06 21:26 ` dpdklab
2024-03-06 21:28 ` dpdklab
2024-03-06 21:31 ` dpdklab
2024-03-06 21:31 ` dpdklab
2024-03-06 21:32 ` dpdklab
2024-03-06 21:32 ` dpdklab
2024-03-06 21:32 ` dpdklab
2024-03-06 21:37 ` dpdklab
2024-03-06 21:37 ` dpdklab
2024-03-06 21:40 ` dpdklab
2024-03-06 21:43 ` dpdklab
2024-03-06 21:44 ` dpdklab
2024-03-06 21:52 ` dpdklab
2024-03-06 21:52 ` dpdklab
2024-03-06 21:52 ` dpdklab
2024-03-06 22:06 ` dpdklab
2024-03-06 22:08 ` dpdklab
2024-03-06 22:20 ` dpdklab
2024-03-06 22:41 ` dpdklab
2024-03-07  1:34 ` 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=202403061847.426Il7pi3359473@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).