automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124926-124927 [PATCH v2 2/2] net/nfp: write link speed to control BAR
Date: Fri, 10 Mar 2023 14:15:17 +0800	[thread overview]
Message-ID: <202303100615.32A6FH6h3032944@localhost.localdomain> (raw)
In-Reply-To: <20230310062542.817107-3-chaoyong.he@corigine.com>

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

_Compilation OK_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Fri, 10 Mar 2023 14:25:41 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 0e3549a75d53a5f37e0ca521c6603e55a9bdbf79

124926-124927 --> 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:[~2023-03-10  6:29 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230310062542.817107-3-chaoyong.he@corigine.com>
2023-03-10  6:15 ` qemudev [this message]
2023-03-10  6:19 ` qemudev
2023-03-10  6:26 ` |SUCCESS| pw124927 " checkpatch
2023-03-10  8:59 ` 0-day Robot
2023-03-10  9:16 |SUCCESS| pw124926-124927 [PATCH] [v2, " dpdklab
2023-03-10  9:21 dpdklab
2023-03-10  9:22 dpdklab
2023-03-10  9:28 dpdklab
2023-03-10  9:28 dpdklab
2023-03-10  9:32 dpdklab
2023-03-10  9:32 dpdklab
2023-03-10  9:34 dpdklab
2023-03-10  9:38 dpdklab
2023-03-10 10:04 dpdklab
2023-03-10 10:16 dpdklab
2023-03-10 10:35 dpdklab
2023-03-10 10:36 dpdklab
2023-03-10 10:39 dpdklab
2023-03-10 10:44 dpdklab
2023-03-10 10:46 dpdklab
2023-03-10 10:47 dpdklab
2023-03-10 10:51 dpdklab
2023-03-10 10:51 dpdklab
2023-03-10 10:55 dpdklab
2023-03-10 10:56 dpdklab
2023-03-10 11:00 dpdklab
2023-03-10 11:05 dpdklab
2023-03-10 11:05 dpdklab
2023-03-10 11:19 dpdklab
2023-03-10 11:30 dpdklab
2023-03-10 11:51 dpdklab
2023-03-10 12:09 dpdklab
2023-03-11  2:37 dpdklab
2023-03-11  3:08 dpdklab
2023-03-11  3:28 dpdklab
2023-03-11 16:46 dpdklab
2023-03-11 16:46 dpdklab
2023-03-11 16:46 dpdklab
2023-03-11 16:51 dpdklab
2023-03-11 16:59 dpdklab
2023-03-11 17:03 dpdklab
2023-03-11 17:07 dpdklab
2023-03-11 17:08 dpdklab
2023-03-11 17:10 dpdklab
2023-03-11 17:13 dpdklab
2023-03-11 17:19 dpdklab
2023-03-11 17:21 dpdklab
2023-03-11 17:23 dpdklab
2023-03-11 18:08 dpdklab
2023-03-11 18:08 dpdklab
2023-03-11 22:53 dpdklab
2023-03-12  0:15 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=202303100615.32A6FH6h3032944@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).