automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137913 [PATCH] common/cnxk: fix loopback port dataflow issue
Date: Mon, 4 Mar 2024 20:11:13 +0800	[thread overview]
Message-ID: <202403041211.424CBDea1001435@localhost.localdomain> (raw)
In-Reply-To: <20240304123335.1769854-1-rbhansali@marvell.com>

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

_Compilation OK_

Submitter: Rahul Bhansali <rbhansali@marvell.com>
Date: Mon, 4 Mar 2024 18:03:35 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
  Branch: for-next-net
  CommitID: cc7ce74402f29c5850eccc5828492135b91135cf

137913 --> 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-03-04 12:36 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240304123335.1769854-1-rbhansali@marvell.com>
2024-03-04 12:11 ` qemudev [this message]
2024-03-04 12:15 ` qemudev
2024-03-04 12:35 ` checkpatch
2024-03-04 13:17 ` |SUCCESS| pw137913 [PATCH] common/cnxk: fix loopback port dataflow i dpdklab
2024-03-04 13:25 ` dpdklab
2024-03-04 13:25 ` dpdklab
2024-03-04 13:26 ` dpdklab
2024-03-04 13:27 ` dpdklab
2024-03-04 13:27 ` dpdklab
2024-03-04 13:28 ` dpdklab
2024-03-04 13:28 ` dpdklab
2024-03-04 13:32 ` dpdklab
2024-03-04 13:32 ` dpdklab
2024-03-04 13:33 ` dpdklab
2024-03-04 13:33 ` dpdklab
2024-03-04 13:33 ` dpdklab
2024-03-04 13:34 ` dpdklab
2024-03-04 13:34 ` dpdklab
2024-03-04 13:34 ` dpdklab
2024-03-04 13:35 ` dpdklab
2024-03-04 13:35 ` dpdklab
2024-03-04 13:35 ` dpdklab
2024-03-04 13:35 ` dpdklab
2024-03-04 13:35 ` dpdklab
2024-03-04 13:36 ` dpdklab
2024-03-04 13:36 ` dpdklab
2024-03-04 13:36 ` dpdklab
2024-03-04 13:36 ` dpdklab
2024-03-04 13:36 ` dpdklab
2024-03-04 13:38 ` dpdklab
2024-03-04 13:38 ` dpdklab
2024-03-04 13:38 ` dpdklab
2024-03-04 13:39 ` dpdklab
2024-03-04 13:39 ` dpdklab
2024-03-04 13:39 ` dpdklab
2024-03-04 13:39 ` dpdklab
2024-03-04 13:40 ` dpdklab
2024-03-04 13:42 ` dpdklab
2024-03-04 13:43 ` dpdklab
2024-03-04 13:47 ` dpdklab
2024-03-04 13:47 ` dpdklab
2024-03-04 13:48 ` dpdklab
2024-03-04 13:48 ` dpdklab
2024-03-04 13:48 ` dpdklab
2024-03-04 13:48 ` dpdklab
2024-03-04 13:48 ` dpdklab
2024-03-04 13:49 ` dpdklab
2024-03-04 13:54 ` dpdklab
2024-03-04 13:55 ` dpdklab
2024-03-04 13:56 ` dpdklab
2024-03-04 13:56 ` dpdklab
2024-03-04 13:57 ` dpdklab
2024-03-04 13:57 ` dpdklab
2024-03-04 13:58 ` dpdklab
2024-03-04 13:58 ` dpdklab
2024-03-04 13:58 ` dpdklab
2024-03-04 13:58 ` dpdklab
2024-03-04 14:00 ` dpdklab
2024-03-04 14:00 ` dpdklab
2024-03-04 14:01 ` dpdklab
2024-03-04 14:01 ` dpdklab
2024-03-04 14:03 ` dpdklab
2024-03-04 14:03 ` dpdklab
2024-03-04 14:05 ` dpdklab
2024-03-04 14:05 ` dpdklab
2024-03-04 14:06 ` dpdklab
2024-03-04 14:06 ` dpdklab
2024-03-04 14:36 ` dpdklab
2024-03-04 14:39 ` dpdklab
2024-03-04 14:52 ` dpdklab
2024-03-04 14:53 ` dpdklab
2024-03-04 15:03 ` dpdklab
2024-03-04 15:28 ` dpdklab
2024-03-08  3:53 ` dpdklab
2024-03-08  4:26 ` dpdklab
2024-03-08  4:58 ` 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=202403041211.424CBDea1001435@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).