automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140336-140337 [PATCH 2/2] net/nfp: support new firmware name scheme
Date: Tue, 28 May 2024 09:03:38 +0800	[thread overview]
Message-ID: <202405280103.44S13bqM3328852@localhost.localdomain> (raw)
In-Reply-To: <20240528012933.2345436-3-chaoyong.he@corigine.com>

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

_Compilation OK_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Tue, 28 May 2024 09:29:32 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 2dbb63594a9a985e2c8639b57f9fcd1468b9de97

140336-140337 --> 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-05-28  1:32 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240528012933.2345436-3-chaoyong.he@corigine.com>
2024-05-28  1:03 ` qemudev [this message]
2024-05-28  1:07 ` qemudev
2024-05-28  1:30 ` |SUCCESS| pw140337 " checkpatch
2024-05-28  2:05 ` |SUCCESS| pw140336-140337 [PATCH] [2/2] net/nfp: support new firmwar dpdklab
2024-05-28  2:05 ` dpdklab
2024-05-28  2:06 ` dpdklab
2024-05-28  2:06 ` dpdklab
2024-05-28  2:06 ` dpdklab
2024-05-28  2:07 ` dpdklab
2024-05-28  2:07 ` dpdklab
2024-05-28  2:08 ` dpdklab
2024-05-28  2:08 ` dpdklab
2024-05-28  2:08 ` dpdklab
2024-05-28  2:09 ` dpdklab
2024-05-28  2:09 ` dpdklab
2024-05-28  2:09 ` dpdklab
2024-05-28  2:10 ` dpdklab
2024-05-28  2:10 ` dpdklab
2024-05-28  2:10 ` dpdklab
2024-05-28  2:10 ` dpdklab
2024-05-28  2:11 ` dpdklab
2024-05-28  2:11 ` dpdklab
2024-05-28  2:11 ` dpdklab
2024-05-28  2:12 ` dpdklab
2024-05-28  2:12 ` dpdklab
2024-05-28  2:13 ` dpdklab
2024-05-28  2:13 ` dpdklab
2024-05-28  2:13 ` dpdklab
2024-05-28  2:13 ` dpdklab
2024-05-28  2:13 ` dpdklab
2024-05-28  2:13 ` dpdklab
2024-05-28  2:14 ` dpdklab
2024-05-28  2:14 ` dpdklab
2024-05-28  2:14 ` dpdklab
2024-05-28  2:14 ` dpdklab
2024-05-28  2:14 ` dpdklab
2024-05-28  2:15 ` dpdklab
2024-05-28  2:15 ` dpdklab
2024-05-28  2:17 ` dpdklab
2024-05-28  2:17 ` dpdklab
2024-05-28  2:23 ` |SUCCESS| pw140337 [PATCH 2/2] net/nfp: support new firmware name scheme 0-day Robot
2024-05-28  2:27 ` |SUCCESS| pw140336-140337 [PATCH] [2/2] net/nfp: support new firmwar dpdklab
2024-05-28  2:28 ` dpdklab
2024-05-28  2:28 ` dpdklab
2024-05-28  2:28 ` dpdklab
2024-05-28  2:28 ` dpdklab
2024-05-28  2:28 ` dpdklab
2024-05-28  2:28 ` dpdklab
2024-05-28  2:29 ` dpdklab
2024-05-28  2:31 ` dpdklab
2024-05-28  2:31 ` dpdklab
2024-05-28  2:31 ` dpdklab
2024-05-28  2:32 ` dpdklab
2024-05-28  2:32 ` dpdklab
2024-05-28  2:32 ` dpdklab
2024-05-28  2:32 ` dpdklab
2024-05-28  2:33 ` dpdklab
2024-05-28  2:33 ` dpdklab
2024-05-28  2:33 ` dpdklab
2024-05-28  2:58 ` dpdklab
2024-05-28  2:59 ` dpdklab
2024-05-28  2:59 ` dpdklab
2024-05-28  2:59 ` dpdklab
2024-05-28  3:00 ` dpdklab
2024-05-28  3:00 ` dpdklab
2024-05-28  3:00 ` dpdklab
2024-05-28  3:01 ` dpdklab
2024-05-28  3:01 ` dpdklab
2024-05-28  3:01 ` dpdklab
2024-05-28  3:02 ` dpdklab
2024-05-28  3:05 ` dpdklab
2024-05-28  3:07 ` dpdklab
2024-05-28  3:07 ` dpdklab
2024-05-28  3:08 ` dpdklab
2024-05-28  3:08 ` dpdklab
2024-05-28  3:10 ` dpdklab
2024-05-28  3:10 ` dpdklab
2024-05-28  3:10 ` dpdklab
2024-05-28  3:11 ` dpdklab
2024-05-28  5:28 ` dpdklab
2024-05-28  5:39 ` dpdklab
2024-05-29 22:32 ` dpdklab
2024-05-29 22:32 ` dpdklab
2024-05-29 22:47 ` 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=202405280103.44S13bqM3328852@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).