automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw132602 [PATCH] net/nfp: fix the Tx performance issue
Date: Fri, 13 Oct 2023 15:27:28 +0800	[thread overview]
Message-ID: <202310130727.39D7RSmN421278@localhost.localdomain> (raw)
In-Reply-To: <20231013074653.3429-1-chaoyong.he@corigine.com>

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

_Compilation OK_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Fri, 13 Oct 2023 15:46:53 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 64b86ec39b328c4a3f7305e233a9399092c0a419

132602 --> 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-10-13  7:48 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231013074653.3429-1-chaoyong.he@corigine.com>
2023-10-13  7:27 ` qemudev [this message]
2023-10-13  7:31 ` qemudev
2023-10-13  7:47 ` checkpatch
2023-10-13  8:59 ` 0-day Robot
2023-10-13 12:30 dpdklab
2023-10-13 12:37 dpdklab
2023-10-13 12:40 dpdklab
2023-10-13 12:40 dpdklab
2023-10-13 12:41 dpdklab
2023-10-13 12:44 dpdklab
2023-10-13 12:48 dpdklab
2023-10-13 12:57 dpdklab
2023-10-13 12:58 dpdklab
2023-10-13 12:58 dpdklab
2023-10-13 12:59 dpdklab
2023-10-13 13:01 dpdklab
2023-10-13 13:02 dpdklab
2023-10-13 13:02 dpdklab
2023-10-13 13:02 dpdklab
2023-10-13 13:04 dpdklab
2023-10-13 13:06 dpdklab
2023-10-13 13:11 dpdklab
2023-10-13 13:12 dpdklab
2023-10-13 13:12 dpdklab
2023-10-13 13:12 dpdklab
2023-10-13 13:13 dpdklab
2023-10-13 13:13 dpdklab
2023-10-13 13:14 dpdklab
2023-10-13 13:14 dpdklab
2023-10-13 13:15 dpdklab
2023-10-13 13:15 dpdklab
2023-10-13 13:16 dpdklab
2023-10-13 13:16 dpdklab
2023-10-13 13:17 dpdklab
2023-10-13 13:17 dpdklab
2023-10-13 13:22 dpdklab
2023-10-13 13:24 dpdklab
2023-10-13 13:31 dpdklab
2023-10-13 13:45 dpdklab
2023-10-13 13:47 dpdklab
2023-10-13 13:51 dpdklab
2023-10-13 13:52 dpdklab
2023-10-13 13:53 dpdklab
2023-10-13 13:54 dpdklab
2023-10-13 13:54 dpdklab
2023-10-13 13:58 dpdklab
2023-10-13 14:09 dpdklab
2023-10-13 14:09 dpdklab
2023-10-13 14:10 dpdklab
2023-10-13 14:11 dpdklab
2023-10-13 14:12 dpdklab
2023-10-13 14:38 dpdklab
2023-10-13 14:46 dpdklab
2023-10-13 15:17 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=202310130727.39D7RSmN421278@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).