automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120682 [PATCH] net/nfp: check whether the generated VF can be used
Date: Sat, 10 Dec 2022 08:18:53 +0800	[thread overview]
Message-ID: <202212100018.2BA0IrI71019074@localhost.localdomain> (raw)
In-Reply-To: <20221209013512.34630-1-chaoyong.he@corigine.com>

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

_Compilation OK_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Fri,  9 Dec 2022 09:35:12 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 175d8374496a8572b2f27216abff344d5ceaa880

120682 --> 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


  parent reply	other threads:[~2022-12-10  0:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221209013512.34630-1-chaoyong.he@corigine.com>
2022-12-09  1:27 ` qemudev
2022-12-09  1:31 ` qemudev
2022-12-09  1:37 ` checkpatch
2022-12-09 15:58 ` 0-day Robot
2022-12-10  0:18 ` qemudev [this message]
2022-12-10  0:19 ` qemudev
2022-12-09  1:59 dpdklab
2022-12-09  1:59 dpdklab
2022-12-09  2:05 dpdklab
2022-12-09  2:12 dpdklab
2022-12-09  2:14 dpdklab
2022-12-09  2:15 dpdklab
2022-12-09  2:19 dpdklab
2022-12-09  2:25 dpdklab
2022-12-09  2:41 dpdklab
2022-12-09  2:43 dpdklab
2022-12-09  2:45 dpdklab
2022-12-09  2:47 dpdklab
2022-12-09  2:47 dpdklab
2022-12-09  2:49 dpdklab
2022-12-09  2:52 dpdklab
2022-12-09  2:56 dpdklab
2022-12-09  3:06 dpdklab
2022-12-09  3:35 dpdklab
2022-12-09  3:36 dpdklab
2022-12-09  3:36 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=202212100018.2BA0IrI71019074@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).