automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138144 [PATCH] net/nfp: fix getting firmware VNIC version
Date: Mon, 11 Mar 2024 09:33:49 +0800	[thread overview]
Message-ID: <202403110133.42B1Xn062008653@localhost.localdomain> (raw)
In-Reply-To: <20240311015414.2514845-1-chaoyong.he@corigine.com>

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

_Compilation OK_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Mon, 11 Mar 2024 09:54:14 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: a2a2ce171d00b8f27c8c43c37d5dd8505d8f2e89

138144 --> 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-11  1:58 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240311015414.2514845-1-chaoyong.he@corigine.com>
2024-03-11  1:33 ` qemudev [this message]
2024-03-11  1:38 ` qemudev
2024-03-11  1:55 ` checkpatch
2024-03-11  2:28 ` |SUCCESS| pw138144 [PATCH] net/nfp: fix getting firmware VNIC versio dpdklab
2024-03-11  2:29 ` dpdklab
2024-03-11  2:30 ` dpdklab
2024-03-11  2:33 ` dpdklab
2024-03-11  2:35 ` dpdklab
2024-03-11  2:35 ` dpdklab
2024-03-11  2:36 ` dpdklab
2024-03-11  2:36 ` dpdklab
2024-03-11  2:36 ` dpdklab
2024-03-11  2:36 ` dpdklab
2024-03-11  2:36 ` dpdklab
2024-03-11  2:36 ` dpdklab
2024-03-11  2:36 ` dpdklab
2024-03-11  2:36 ` dpdklab
2024-03-11  2:37 ` dpdklab
2024-03-11  2:37 ` dpdklab
2024-03-11  2:37 ` dpdklab
2024-03-11  2:37 ` dpdklab
2024-03-11  2:38 ` dpdklab
2024-03-11  2:38 ` dpdklab
2024-03-11  2:38 ` dpdklab
2024-03-11  2:38 ` dpdklab
2024-03-11  2:38 ` dpdklab
2024-03-11  2:38 ` dpdklab
2024-03-11  2:38 ` dpdklab
2024-03-11  2:39 ` dpdklab
2024-03-11  2:39 ` dpdklab
2024-03-11  2:39 ` dpdklab
2024-03-11  2:39 ` dpdklab
2024-03-11  2:39 ` dpdklab
2024-03-11  2:39 ` dpdklab
2024-03-11  2:40 ` dpdklab
2024-03-11  2:40 ` dpdklab
2024-03-11  2:40 ` dpdklab
2024-03-11  2:40 ` dpdklab
2024-03-11  2:40 ` dpdklab
2024-03-11  2:41 ` dpdklab
2024-03-11  2:41 ` dpdklab
2024-03-11  2:41 ` dpdklab
2024-03-11  2:41 ` dpdklab
2024-03-11  2:41 ` dpdklab
2024-03-11  2:41 ` dpdklab
2024-03-11  2:42 ` dpdklab
2024-03-11  2:42 ` dpdklab
2024-03-11  2:42 ` |SUCCESS| pw138144 [PATCH] net/nfp: fix getting firmware VNIC version 0-day Robot
2024-03-11  2:43 ` |SUCCESS| pw138144 [PATCH] net/nfp: fix getting firmware VNIC versio dpdklab
2024-03-11  2:43 ` dpdklab
2024-03-11  2:44 ` dpdklab
2024-03-11  2:44 ` dpdklab
2024-03-11  2:44 ` dpdklab
2024-03-11  2:45 ` dpdklab
2024-03-11  2:46 ` dpdklab
2024-03-11  2:47 ` dpdklab
2024-03-11  2:47 ` dpdklab
2024-03-11  2:47 ` dpdklab
2024-03-11  2:48 ` dpdklab
2024-03-11  2:49 ` dpdklab
2024-03-11  2:49 ` dpdklab
2024-03-11  2:49 ` dpdklab
2024-03-11  2:50 ` dpdklab
2024-03-11  2:51 ` dpdklab
2024-03-11  2:52 ` dpdklab
2024-03-11  2:53 ` dpdklab
2024-03-11  2:54 ` dpdklab
2024-03-11  2:57 ` dpdklab
2024-03-11  3:29 ` dpdklab
2024-03-14 11:48 ` dpdklab
2024-03-14 12:27 ` 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=202403110133.42B1Xn062008653@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).