automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139014 [PATCH] net/nfp: use Tx ring pointer write back
Date: Mon, 1 Apr 2024 14:34:40 +0800	[thread overview]
Message-ID: <202404010634.4316YekJ707366@localhost.localdomain> (raw)
In-Reply-To: <20240401065622.106253-1-chaoyong.he@corigine.com>

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

_Compilation OK_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Mon,  1 Apr 2024 14:56:22 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: a9778aad62470a38ccbb4e09a2a6bf0cc2e0e36d

139014 --> 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-04-01  6:59 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240401065622.106253-1-chaoyong.he@corigine.com>
2024-04-01  6:34 ` qemudev [this message]
2024-04-01  6:39 ` qemudev
2024-04-01  6:57 ` checkpatch
2024-04-01  7:45 ` 0-day Robot
2024-04-01  7:50 ` dpdklab
2024-04-01  7:52 ` dpdklab
2024-04-01  7:53 ` dpdklab
2024-04-01  7:53 ` dpdklab
2024-04-01  7:54 ` dpdklab
2024-04-01  7:54 ` dpdklab
2024-04-01  7:54 ` dpdklab
2024-04-01  7:54 ` dpdklab
2024-04-01  7:55 ` dpdklab
2024-04-01  7:55 ` dpdklab
2024-04-01  7:56 ` dpdklab
2024-04-01  7:56 ` dpdklab
2024-04-01  7:56 ` dpdklab
2024-04-01  7:57 ` dpdklab
2024-04-01  7:57 ` dpdklab
2024-04-01  7:58 ` dpdklab
2024-04-01  7:58 ` dpdklab
2024-04-01  7:59 ` dpdklab
2024-04-01  8:00 ` dpdklab
2024-04-01  8:00 ` dpdklab
2024-04-01  8:01 ` dpdklab
2024-04-01  8:01 ` dpdklab
2024-04-01  8:02 ` dpdklab
2024-04-01  8:02 ` dpdklab
2024-04-01  8:03 ` dpdklab
2024-04-01  8:03 ` dpdklab
2024-04-01  8:04 ` dpdklab
2024-04-01  8:05 ` dpdklab
2024-04-01  8:05 ` dpdklab
2024-04-01  8:06 ` dpdklab
2024-04-01  8:06 ` dpdklab
2024-04-01  8:08 ` dpdklab
2024-04-01  8:09 ` dpdklab
2024-04-01  8:09 ` dpdklab
2024-04-01  8:10 ` dpdklab
2024-04-01  8:10 ` dpdklab
2024-04-01  8:11 ` dpdklab
2024-04-01  8:11 ` dpdklab
2024-04-01  8:11 ` dpdklab
2024-04-01  8:12 ` dpdklab
2024-04-01  8:12 ` dpdklab
2024-04-01  8:13 ` dpdklab
2024-04-01  8:13 ` dpdklab
2024-04-01  8:13 ` dpdklab
2024-04-01  8:14 ` dpdklab
2024-04-01  8:14 ` dpdklab
2024-04-01  8:14 ` dpdklab
2024-04-01  8:15 ` dpdklab
2024-04-01  8:15 ` dpdklab
2024-04-01  8:15 ` dpdklab
2024-04-01  8:16 ` dpdklab
2024-04-01  8:16 ` dpdklab
2024-04-01  8:16 ` dpdklab
2024-04-01  8:17 ` dpdklab
2024-04-01  8:17 ` dpdklab
2024-04-01  8:17 ` dpdklab
2024-04-01  8:18 ` dpdklab
2024-04-01  8:18 ` dpdklab
2024-04-01  8:18 ` dpdklab
2024-04-01  8:19 ` dpdklab
2024-04-01  8:19 ` dpdklab
2024-04-01  8:20 ` dpdklab
2024-04-01  8:20 ` dpdklab
2024-04-01  8:20 ` dpdklab
2024-04-01  8:20 ` dpdklab
2024-04-01  8:20 ` dpdklab
2024-04-01  8:21 ` dpdklab
2024-04-01  8:21 ` dpdklab
2024-04-01  8:21 ` dpdklab
2024-04-01  8:21 ` dpdklab
2024-04-01  8:21 ` dpdklab
2024-04-01  8:22 ` dpdklab
2024-04-01  8:22 ` dpdklab
2024-04-01  8:22 ` dpdklab
2024-04-01  8:23 ` dpdklab
2024-04-01  8:30 ` dpdklab
2024-04-01  8:31 ` dpdklab
2024-04-01  8:57 ` dpdklab
2024-04-01  9:08 ` dpdklab
2024-04-01  9:11 ` dpdklab
2024-04-01  9:33 ` dpdklab
2024-04-03 12:35 ` dpdklab
2024-04-03 12:36 ` dpdklab
2024-04-03 13:06 ` dpdklab
2024-04-03 13:07 ` dpdklab
2024-04-03 13:38 ` 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=202404010634.4316YekJ707366@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).