automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125877-125889 [PATCH 13/13] net/nfp: modify the logic of some NFDk function
Date: Mon, 10 Apr 2023 18:52:42 +0800	[thread overview]
Message-ID: <202304101052.33AAqgC41743414@localhost.localdomain> (raw)
In-Reply-To: <20230410110015.2973660-14-chaoyong.he@corigine.com>

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

_Compilation OK_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Mon, 10 Apr 2023 19:00:03 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 40a62da00b3619ed72be6ceeded89d1fe62ed027

125877-125889 --> 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-04-10 11:06 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230410110015.2973660-14-chaoyong.he@corigine.com>
2023-04-10 10:52 ` qemudev [this message]
2023-04-10 10:56 ` qemudev
2023-04-10 11:05 ` |SUCCESS| pw125889 " checkpatch
2023-04-10 11:58 ` 0-day Robot
2023-04-10 11:37 |SUCCESS| pw125877-125889 [PATCH] [13/13] " dpdklab
2023-04-10 11:39 dpdklab
2023-04-10 11:44 dpdklab
2023-04-10 11:44 dpdklab
2023-04-10 11:46 dpdklab
2023-04-10 11:46 dpdklab
2023-04-10 11:47 dpdklab
2023-04-10 11:50 dpdklab
2023-04-10 11:50 dpdklab
2023-04-10 11:50 dpdklab
2023-04-10 11:51 dpdklab
2023-04-10 11:52 dpdklab
2023-04-10 11:55 dpdklab
2023-04-10 11:57 dpdklab
2023-04-10 11:59 dpdklab
2023-04-10 12:00 dpdklab
2023-04-10 12:00 dpdklab
2023-04-10 12:01 dpdklab
2023-04-10 12:03 dpdklab
2023-04-10 12:10 dpdklab
2023-04-10 12:11 dpdklab
2023-04-10 12:12 dpdklab
2023-04-10 12:15 dpdklab
2023-04-10 12:16 dpdklab
2023-04-10 12:16 dpdklab
2023-04-10 12:17 dpdklab
2023-04-10 12:17 dpdklab
2023-04-10 12:18 dpdklab
2023-04-10 12:18 dpdklab
2023-04-10 12:19 dpdklab
2023-04-10 12:20 dpdklab
2023-04-10 12:22 dpdklab
2023-04-10 12:23 dpdklab
2023-04-10 12:24 dpdklab
2023-04-10 12:29 dpdklab
2023-04-10 12:36 dpdklab
2023-04-10 12:36 dpdklab
2023-04-10 12:39 dpdklab
2023-04-10 12:47 dpdklab
2023-04-10 12:47 dpdklab
2023-04-10 12:51 dpdklab
2023-04-10 12:59 dpdklab
2023-04-10 12:59 dpdklab
2023-04-10 13:00 dpdklab
2023-04-10 13:02 dpdklab
2023-04-10 13:04 dpdklab
2023-04-10 13:04 dpdklab
2023-04-10 13:09 dpdklab
2023-04-10 13:13 dpdklab
2023-04-10 13:29 dpdklab
2023-04-10 13:33 dpdklab
2023-04-10 13:41 dpdklab
2023-04-10 19:00 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=202304101052.33AAqgC41743414@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).