automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144807 [PATCH v3 1/1] net/octeon_ep: add device removal event callback
Date: Tue, 1 Oct 2024 16:17:45 +0800	[thread overview]
Message-ID: <202410010817.4918Hj061135917@localhost.localdomain> (raw)
In-Reply-To: <20241001083837.1308452-1-vattunuru@marvell.com>

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

_Compilation OK_

Submitter: Vamsi Krishna <vattunuru@marvell.com>
Date: Tue, 1 Oct 2024 14:08:37 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
  Branch: for-next-net
  CommitID: ae03728dd31175d055f7df4e141f9944eccf9444

144807 --> 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-10-01  8:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241001083837.1308452-1-vattunuru@marvell.com>
2024-10-01  8:17 ` qemudev [this message]
2024-10-01  8:22 ` qemudev
2024-10-01  8:39 ` checkpatch
2024-10-01 15:32 ` |SUCCESS| pw144807 [PATCH] [v3,1/1] net/octeon_ep: add device remova dpdklab
2024-10-01 15:36 ` dpdklab
2024-10-01 15:44 ` dpdklab
2024-10-01 15:53 ` dpdklab
2024-10-01 15:58 ` dpdklab
2024-10-01 16:38 ` |PENDING| " dpdklab
2024-10-01 16:55 ` |SUCCESS| " dpdklab
2024-10-01 17:33 ` |PENDING| " dpdklab
2024-10-01 17:55 ` |SUCCESS| " dpdklab
2024-10-01 18:04 ` dpdklab
2024-10-01 19:37 ` |PENDING| " dpdklab
2024-10-01 20:12 ` |SUCCESS| " dpdklab
2024-10-01 20:59 ` dpdklab
2024-10-01 21:50 ` dpdklab
2024-10-01 22:03 ` dpdklab
2024-10-01 22:10 ` dpdklab
2024-10-01 22:30 ` dpdklab
2024-10-01 22:32 ` dpdklab
2024-10-02  1:42 ` 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=202410010817.4918Hj061135917@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).