automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw132146 [PATCH v3] testpmd: add hairpin-map parameter
Date: Thu, 28 Sep 2023 23:17:31 +0800	[thread overview]
Message-ID: <202309281517.38SFHVoa221314@localhost.localdomain> (raw)
In-Reply-To: <20230928153605.759397-1-getelson@nvidia.com>

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

_Compilation OK_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thu, 28 Sep 2023 18:36:05 +0300
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: b9e98c46e0e1d8490a86c663a0b9266fde1e3e80

132146 --> 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-09-28 15:38 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230928153605.759397-1-getelson@nvidia.com>
2023-09-28 15:17 ` qemudev [this message]
2023-09-28 15:21 ` qemudev
2023-09-28 15:37 ` |WARNING| " checkpatch
2023-09-28 16:39 ` |SUCCESS| " 0-day Robot
2023-09-28 23:55 |SUCCESS| pw132146 [PATCH] [v3] " dpdklab
2023-09-28 23:55 dpdklab
2023-09-28 23:58 dpdklab
2023-09-28 23:59 dpdklab
2023-09-28 23:59 dpdklab
2023-09-29  0:00 dpdklab
2023-09-29  0:00 dpdklab
2023-09-29  0:16 dpdklab
2023-09-29  0:23 dpdklab
2023-09-29  0:23 dpdklab
2023-09-29  0:24 dpdklab
2023-09-29  0:25 dpdklab
2023-09-29  0:25 dpdklab
2023-09-29  0:25 dpdklab
2023-09-29  0:26 dpdklab
2023-09-29  0:26 dpdklab
2023-09-29  0:26 dpdklab
2023-09-29  0:26 dpdklab
2023-09-29  0:26 dpdklab
2023-09-29  0:26 dpdklab
2023-09-29  0:27 dpdklab
2023-09-29  0:27 dpdklab
2023-09-29  0:27 dpdklab
2023-09-29  0:27 dpdklab
2023-09-29  0:28 dpdklab
2023-09-29  0:28 dpdklab
2023-09-29  0:30 dpdklab
2023-09-29  0:31 dpdklab
2023-09-29  0:36 dpdklab
2023-09-29  0:40 dpdklab
2023-09-29  0:41 dpdklab
2023-09-29  0:44 dpdklab
2023-09-29  0:46 dpdklab
2023-09-29  0:47 dpdklab
2023-09-29  0:48 dpdklab
2023-09-29  0:54 dpdklab
2023-09-29  0:54 dpdklab
2023-09-29  0:57 dpdklab
2023-09-29  0:58 dpdklab
2023-09-29  1:03 dpdklab
2023-09-29  1:03 dpdklab
2023-09-29  1:04 dpdklab
2023-09-29  1:24 dpdklab
2023-09-29  1:26 dpdklab
2023-09-29  1:27 dpdklab
2023-09-29  1:27 dpdklab
2023-09-29  1:28 dpdklab
2023-09-29  1:32 dpdklab
2023-09-29  1:33 dpdklab
2023-09-29  4:40 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=202309281517.38SFHVoa221314@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).