From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138752-138753 [RFC 2/2] testpmd: Add speed lanes to testpmd config and show command
Date: Sat, 23 Mar 2024 06:03:52 +0800 [thread overview]
Message-ID: <202403222203.42MM3qIA2034528@localhost.localdomain> (raw)
In-Reply-To: <20240322222543.23548-3-damodharam.ammepalli@broadcom.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138753
_Compilation OK_
Submitter: Damodharam Ammepalli <damodharam.ammepalli@broadcom.com>
Date: Fri, 22 Mar 2024 15:25:42 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 0d7f7a7171484a12f6059f71a2e1a82c5bfaaa89
138752-138753 --> 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
next parent reply other threads:[~2024-03-22 22:29 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240322222543.23548-3-damodharam.ammepalli@broadcom.com>
2024-03-22 22:03 ` qemudev [this message]
2024-03-22 22:08 ` qemudev
2024-03-22 22:28 ` |SUCCESS| pw138753 " checkpatch
2024-03-22 23:24 ` |FAILURE| " 0-day Robot
2024-03-23 0:24 ` |SUCCESS| pw138752-138753 [PATCH] [RFC,2/2] testpmd: Add speed lanes dpdklab
2024-03-23 0:24 ` dpdklab
2024-03-23 0:24 ` dpdklab
2024-03-23 0:36 ` dpdklab
2024-03-23 0:36 ` dpdklab
2024-03-23 0:37 ` dpdklab
2024-03-23 0:37 ` dpdklab
2024-03-23 0:37 ` dpdklab
2024-03-23 0:37 ` dpdklab
2024-03-23 0:37 ` dpdklab
2024-03-23 0:38 ` dpdklab
2024-03-23 0:38 ` dpdklab
2024-03-23 0:38 ` dpdklab
2024-03-23 0:39 ` dpdklab
2024-03-23 0:43 ` dpdklab
2024-03-23 0:44 ` dpdklab
2024-03-23 0:44 ` dpdklab
2024-03-23 0:45 ` dpdklab
2024-03-23 0:45 ` dpdklab
2024-03-23 0:45 ` dpdklab
2024-03-23 0:46 ` dpdklab
2024-03-23 0:46 ` dpdklab
2024-03-23 0:46 ` dpdklab
2024-03-23 0:46 ` dpdklab
2024-03-23 0:47 ` dpdklab
2024-03-23 0:47 ` dpdklab
2024-03-23 0:49 ` dpdklab
2024-03-23 0:50 ` dpdklab
2024-03-23 0:56 ` dpdklab
2024-03-23 0:57 ` dpdklab
2024-03-23 0:58 ` dpdklab
2024-03-23 1:01 ` dpdklab
2024-03-23 1:02 ` dpdklab
2024-03-23 1:03 ` dpdklab
2024-03-23 1:05 ` dpdklab
2024-03-23 1:06 ` dpdklab
2024-03-23 1:07 ` dpdklab
2024-03-23 1:08 ` dpdklab
2024-03-23 1:08 ` dpdklab
2024-03-23 1:09 ` dpdklab
2024-03-23 1:10 ` dpdklab
2024-03-23 1:10 ` dpdklab
2024-03-23 1:10 ` dpdklab
2024-03-23 1:11 ` dpdklab
2024-03-23 1:11 ` dpdklab
2024-03-23 1:12 ` dpdklab
2024-03-23 1:12 ` dpdklab
2024-03-23 1:12 ` dpdklab
2024-03-23 1:15 ` dpdklab
2024-03-23 1:16 ` dpdklab
2024-03-23 1:17 ` dpdklab
2024-03-23 1:19 ` dpdklab
2024-03-23 1:21 ` dpdklab
2024-03-23 1:24 ` dpdklab
2024-03-23 1:24 ` dpdklab
2024-03-23 1:26 ` dpdklab
2024-03-23 1:26 ` dpdklab
2024-03-23 1:27 ` dpdklab
2024-03-23 1:29 ` dpdklab
2024-03-23 1:30 ` dpdklab
2024-03-23 1:31 ` dpdklab
2024-03-23 1:32 ` dpdklab
2024-03-23 1:33 ` dpdklab
2024-03-23 1:34 ` dpdklab
2024-03-23 1:38 ` dpdklab
2024-03-23 1:46 ` dpdklab
2024-03-23 1:51 ` dpdklab
2024-03-23 2:09 ` dpdklab
2024-03-23 2:12 ` dpdklab
2024-03-23 2:29 ` dpdklab
2024-03-23 2:43 ` dpdklab
2024-03-23 2:56 ` dpdklab
2024-03-23 2:59 ` dpdklab
2024-03-23 3:00 ` dpdklab
2024-03-23 3:33 ` dpdklab
2024-03-23 5:06 ` dpdklab
2024-03-24 17:53 ` dpdklab
2024-03-24 18:29 ` 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=202403222203.42MM3qIA2034528@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).