automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125096 [PATCH] app/testpmd: support dump ethdev private cmd
Date: Wed, 15 Mar 2023 08:48:11 +0800	[thread overview]
Message-ID: <202303150048.32F0mBgo3172309@localhost.localdomain> (raw)
In-Reply-To: <20230314115035.33356-1-fengchengwen@huawei.com>

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

_Compilation OK_

Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Tue, 14 Mar 2023 11:50:35 +0000
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 6a7534e91dcbc169018b3fc4c2d82f38cb0fbc72

125096 --> 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:[~2023-03-15  1:02 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230314115035.33356-1-fengchengwen@huawei.com>
2023-03-14 11:58 ` checkpatch
2023-03-14 14:39 ` 0-day Robot
2023-03-15  0:48 ` qemudev [this message]
2023-03-15  0:48 ` qemudev
2023-03-14 13:30 dpdklab
2023-03-14 13:36 dpdklab
2023-03-14 13:40 dpdklab
2023-03-14 13:41 dpdklab
2023-03-14 13:42 dpdklab
2023-03-14 13:42 dpdklab
2023-03-14 13:44 dpdklab
2023-03-14 13:47 dpdklab
2023-03-14 13:48 dpdklab
2023-03-14 13:50 dpdklab
2023-03-14 13:52 dpdklab
2023-03-14 13:57 dpdklab
2023-03-14 14:01 dpdklab
2023-03-14 14:34 dpdklab
2023-03-14 14:40 dpdklab
2023-03-14 14:45 dpdklab
2023-03-14 14:47 dpdklab
2023-03-14 14:47 dpdklab
2023-03-14 14:49 dpdklab
2023-03-14 14:51 dpdklab
2023-03-14 14:53 dpdklab
2023-03-14 14:53 dpdklab
2023-03-14 14:54 dpdklab
2023-03-14 14:56 dpdklab
2023-03-14 14:56 dpdklab
2023-03-14 15:04 dpdklab
2023-03-14 15:05 dpdklab
2023-03-14 16:24 dpdklab
2023-03-14 22:36 dpdklab
2023-03-14 22:52 dpdklab
2023-03-14 22:54 dpdklab
2023-03-14 23:15 dpdklab
2023-03-15 15:40 dpdklab
2023-03-15 15:44 dpdklab
2023-03-15 15:50 dpdklab
2023-03-15 15:55 dpdklab
2023-03-15 15:59 dpdklab
2023-03-15 16:11 dpdklab
2023-03-15 16:11 dpdklab
2023-03-15 16:14 dpdklab
2023-03-15 16:20 dpdklab
2023-03-15 16:28 dpdklab
2023-03-15 16:30 dpdklab
2023-03-15 16:35 dpdklab
2023-03-15 16:47 dpdklab
2023-03-15 16:56 dpdklab
2023-03-15 16:58 dpdklab
2023-03-15 17:01 dpdklab
2023-03-15 17:02 dpdklab
2023-03-15 17:07 dpdklab
2023-03-15 17:14 dpdklab
2023-03-15 17:16 dpdklab
2023-03-15 17:20 dpdklab
2023-03-15 17:24 dpdklab
2023-03-15 17:31 dpdklab
2023-03-15 17:35 dpdklab
2023-03-15 17:38 dpdklab
2023-03-15 17:47 dpdklab
2023-03-15 17:53 dpdklab
2023-03-15 17:54 dpdklab
2023-03-16 12:45 dpdklab
2023-03-16 13:51 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=202303150048.32F0mBgo3172309@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).