From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122365 [PATCH v4] app/testpmd: fix interactive mode with no ports
Date: Fri, 20 Jan 2023 01:37:56 +0800 [thread overview]
Message-ID: <202301191737.30JHbuIJ3083182@localhost.localdomain> (raw)
In-Reply-To: <20230119174559.16120-1-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122365
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thu, 19 Jan 2023 19:45:59 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: f2ea2a08e57f7aa539140d08973c908503abf969
122365 --> 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:[~2023-01-19 17:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230119174559.16120-1-getelson@nvidia.com>
2023-01-19 17:37 ` qemudev [this message]
2023-01-19 17:41 ` qemudev
2023-01-19 17:46 ` checkpatch
2023-01-19 19:23 ` |FAILURE| " 0-day Robot
2023-01-19 18:13 |SUCCESS| pw122365 [PATCH] [v4] " dpdklab
2023-01-19 18:15 dpdklab
2023-01-19 18:17 dpdklab
2023-01-19 18:18 dpdklab
2023-01-19 18:19 dpdklab
2023-01-19 18:21 dpdklab
2023-01-19 18:28 dpdklab
2023-01-19 18:35 dpdklab
2023-01-19 21:50 dpdklab
2023-01-20 4:56 dpdklab
2023-01-20 4:57 dpdklab
2023-01-20 4:57 dpdklab
2023-01-20 4:57 dpdklab
2023-01-20 4:58 dpdklab
2023-01-20 4:58 dpdklab
2023-01-20 4:59 dpdklab
2023-01-20 5:00 dpdklab
2023-01-20 5:12 dpdklab
2023-01-20 15:53 dpdklab
2023-01-21 11:05 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=202301191737.30JHbuIJ3083182@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).