automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120684 [PATCH] net/nfp: add support reading linkspeed from port table
Date: Sat, 10 Dec 2022 08:17:50 +0800	[thread overview]
Message-ID: <202212100017.2BA0HoLV1018968@localhost.localdomain> (raw)
In-Reply-To: <20221209024359.15245-1-chaoyong.he@corigine.com>

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

_Compilation OK_

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

120684 --> 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:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221209024359.15245-1-chaoyong.he@corigine.com>
2022-12-09  2:36 ` qemudev
2022-12-09  2:40 ` qemudev
2022-12-09  2:45 ` checkpatch
2022-12-09 16:18 ` 0-day Robot
2022-12-10  0:17 ` qemudev [this message]
2022-12-10  0:18 ` qemudev
2022-12-09  4:29 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2022-12-09  4:29 dpdklab
2022-12-09  4:26 dpdklab
2022-12-09  4:26 dpdklab
2022-12-09  4:23 dpdklab
2022-12-09  4:18 dpdklab
2022-12-09  4:12 dpdklab
2022-12-09  4:11 dpdklab
2022-12-09  4:10 dpdklab
2022-12-09  4:07 dpdklab
2022-12-09  4:04 dpdklab
2022-12-09  3:56 dpdklab
2022-12-09  3:53 dpdklab
2022-12-09  3:49 dpdklab
2022-12-09  3:35 dpdklab
2022-12-09  3:31 dpdklab
2022-12-09  3:27 dpdklab
2022-12-09  3:24 dpdklab
2022-12-09  3:17 dpdklab
2022-12-09  3:11 dpdklab
2022-12-09  3:10 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=202212100017.2BA0HoLV1018968@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).