From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123847 [PATCH v3] ethdev: telemetry xstats support hide zero
Date: Tue, 14 Feb 2023 09:29:44 +0800 [thread overview]
Message-ID: <202302140129.31E1TiPA3796309@localhost.localdomain> (raw)
In-Reply-To: <20230214013506.49152-1-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123847
_Compilation OK_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Tue, 14 Feb 2023 01:35:06 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 0bc202f1035f0cc258a69e9f0383f7bd430ec070
123847 --> 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-02-14 1:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230214013506.49152-1-fengchengwen@huawei.com>
2023-02-14 1:29 ` qemudev [this message]
2023-02-14 1:33 ` qemudev
2023-02-14 1:42 ` checkpatch
2023-02-14 4:19 ` 0-day Robot
2023-02-14 2:06 |SUCCESS| pw123847 [PATCH] [v3] " dpdklab
2023-02-14 2:10 dpdklab
2023-02-14 2:11 dpdklab
2023-02-14 2:11 dpdklab
2023-02-14 2:17 dpdklab
2023-02-14 2:18 dpdklab
2023-02-14 2:22 dpdklab
2023-02-14 2:23 dpdklab
2023-02-14 2:25 dpdklab
2023-02-14 2:30 dpdklab
2023-02-14 7:41 dpdklab
2023-02-14 7:52 dpdklab
2023-02-14 8:01 dpdklab
2023-02-14 8:04 dpdklab
2023-02-14 8:08 dpdklab
2023-02-14 8:10 dpdklab
2023-02-14 8:12 dpdklab
2023-02-14 8:14 dpdklab
2023-02-14 8:18 dpdklab
2023-02-14 8:19 dpdklab
2023-02-14 8:28 dpdklab
2023-02-14 8:34 dpdklab
2023-02-14 8:35 dpdklab
2023-02-14 8:35 dpdklab
2023-02-15 2:04 dpdklab
2023-02-16 1:53 dpdklab
2023-02-18 2:12 dpdklab
2023-02-18 21:06 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=202302140129.31E1TiPA3796309@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).