automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138217 [PATCH v4] app/eventdev: support DMA adapter test
Date: Tue, 12 Mar 2024 22:10:27 +0800	[thread overview]
Message-ID: <202403121410.42CEARTd3285712@localhost.localdomain> (raw)
In-Reply-To: <20240312143023.2651468-1-amitprakashs@marvell.com>

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

_Compilation OK_

Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Tue, 12 Mar 2024 20:00:23 +0530
DPDK git baseline: Repo:dpdk-next-eventdev
  Branch: for-main
  CommitID: a86f381b826660e88794754c41d3aec79ce9b87c

138217 --> 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-12 14:35 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240312143023.2651468-1-amitprakashs@marvell.com>
2024-03-12 14:10 ` qemudev [this message]
2024-03-12 14:14 ` qemudev
2024-03-12 14:32 ` checkpatch
2024-03-12 15:22 ` 0-day Robot
2024-03-12 16:02 ` |SUCCESS| pw138217 [PATCH] [v4] app/eventdev: support DMA adapter te dpdklab
2024-03-12 16:02 ` dpdklab
2024-03-12 16:03 ` dpdklab
2024-03-12 16:03 ` dpdklab
2024-03-12 16:11 ` dpdklab
2024-03-12 16:19 ` dpdklab
2024-03-12 16:19 ` dpdklab
2024-03-12 16:19 ` dpdklab
2024-03-12 16:19 ` dpdklab
2024-03-12 16:20 ` dpdklab
2024-03-12 16:20 ` dpdklab
2024-03-12 16:20 ` dpdklab
2024-03-12 16:21 ` dpdklab
2024-03-12 16:21 ` dpdklab
2024-03-12 16:21 ` dpdklab
2024-03-12 16:22 ` dpdklab
2024-03-12 16:22 ` dpdklab
2024-03-12 16:22 ` dpdklab
2024-03-12 16:22 ` dpdklab
2024-03-12 16:22 ` dpdklab
2024-03-12 16:23 ` dpdklab
2024-03-12 16:23 ` dpdklab
2024-03-12 16:23 ` dpdklab
2024-03-12 16:23 ` dpdklab
2024-03-12 16:23 ` dpdklab
2024-03-12 16:24 ` dpdklab
2024-03-12 16:24 ` dpdklab
2024-03-12 16:24 ` dpdklab
2024-03-12 16:24 ` dpdklab
2024-03-12 16:24 ` dpdklab
2024-03-12 16:25 ` dpdklab
2024-03-12 16:25 ` dpdklab
2024-03-12 16:25 ` dpdklab
2024-03-12 16:25 ` dpdklab
2024-03-12 16:25 ` dpdklab
2024-03-12 16:25 ` dpdklab
2024-03-12 16:25 ` dpdklab
2024-03-12 16:26 ` dpdklab
2024-03-12 16:26 ` dpdklab
2024-03-12 16:26 ` dpdklab
2024-03-12 16:26 ` dpdklab
2024-03-12 16:26 ` dpdklab
2024-03-12 16:26 ` dpdklab
2024-03-12 16:27 ` dpdklab
2024-03-12 16:27 ` dpdklab
2024-03-12 16:27 ` dpdklab
2024-03-12 16:27 ` dpdklab
2024-03-12 16:27 ` dpdklab
2024-03-12 16:27 ` dpdklab
2024-03-12 16:28 ` dpdklab
2024-03-12 16:28 ` dpdklab
2024-03-12 16:28 ` dpdklab
2024-03-12 16:28 ` dpdklab
2024-03-12 16:28 ` dpdklab
2024-03-12 16:29 ` dpdklab
2024-03-12 16:29 ` dpdklab
2024-03-12 16:30 ` dpdklab
2024-03-12 16:30 ` dpdklab
2024-03-12 16:31 ` dpdklab
2024-03-12 16:31 ` dpdklab
2024-03-12 16:32 ` dpdklab
2024-03-12 16:34 ` dpdklab
2024-03-12 16:35 ` dpdklab
2024-03-12 16:40 ` dpdklab
2024-03-12 16:46 ` dpdklab
2024-03-12 17:35 ` dpdklab
2024-03-12 17:46 ` dpdklab
2024-03-16  2:18 ` dpdklab
2024-03-16  2:55 ` 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=202403121410.42CEARTd3285712@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).