From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125183 [PATCH v2] app/testpmd: dump private info in 'show port info'
Date: Thu, 16 Mar 2023 17:36:38 +0800 [thread overview]
Message-ID: <202303160936.32G9ac5d204982@localhost.localdomain> (raw)
In-Reply-To: <20230316093216.18516-1-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125183
_Compilation OK_
Submitter: fengchengwen <fengchengwen@huawei.com>
Date: Thu, 16 Mar 2023 09:32:16 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 6a7534e91dcbc169018b3fc4c2d82f38cb0fbc72
125183 --> 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-03-16 9:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230316093216.18516-1-fengchengwen@huawei.com>
2023-03-16 9:36 ` qemudev [this message]
2023-03-16 9:40 ` checkpatch
2023-03-16 9:40 ` qemudev
2023-03-16 11:59 ` 0-day Robot
2023-03-16 13:53 |SUCCESS| pw125183 [PATCH] [v2] " dpdklab
2023-03-16 13:59 dpdklab
2023-03-16 13:59 dpdklab
2023-03-16 14:04 dpdklab
2023-03-16 14:06 dpdklab
2023-03-16 14:06 dpdklab
2023-03-16 14:06 dpdklab
2023-03-16 14:08 dpdklab
2023-03-16 14:10 dpdklab
2023-03-16 14:11 dpdklab
2023-03-16 14:15 dpdklab
2023-03-16 14:20 dpdklab
2023-03-16 14:25 dpdklab
2023-03-16 16:23 dpdklab
2023-03-16 17:00 dpdklab
2023-03-17 0:25 dpdklab
2023-03-18 14: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=202303160936.32G9ac5d204982@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).