From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123487 [PATCH] telemetry: fix repeat display when callback don't init dict
Date: Thu, 9 Feb 2023 09:22:00 +0800 [thread overview]
Message-ID: <202302090122.3191M0283318626@localhost.localdomain> (raw)
In-Reply-To: <20230209012533.45962-1-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123487
_Compilation OK_
Submitter: fengchengwen <fengchengwen@huawei.com>
Date: Thu, 9 Feb 2023 01:25:33 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: a0c837ad1fb5b6a8b10a284ffeb5f9e31bd8ff00
123487 --> 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-09 1:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230209012533.45962-1-fengchengwen@huawei.com>
2023-02-09 1:22 ` qemudev [this message]
2023-02-09 1:25 ` qemudev
2023-02-09 1:31 ` checkpatch
2023-02-09 2:39 ` |FAILURE| " 0-day Robot
2023-02-09 1:52 |SUCCESS| " dpdklab
2023-02-09 1:54 dpdklab
2023-02-09 1:59 dpdklab
2023-02-09 1:59 dpdklab
2023-02-09 1:59 dpdklab
2023-02-09 2:03 dpdklab
2023-02-09 2:06 dpdklab
2023-02-09 2:06 dpdklab
2023-02-09 2:06 dpdklab
2023-02-09 2:08 dpdklab
2023-02-09 2:08 dpdklab
2023-02-09 2:10 dpdklab
2023-02-09 2:14 dpdklab
2023-02-09 3:31 dpdklab
2023-02-10 4:11 dpdklab
2023-02-10 4:21 dpdklab
2023-02-10 4:33 dpdklab
2023-02-10 4:37 dpdklab
2023-02-10 4:53 dpdklab
2023-02-10 4:59 dpdklab
2023-02-10 5:03 dpdklab
2023-02-10 5:09 dpdklab
2023-02-10 5:12 dpdklab
2023-02-10 5:14 dpdklab
2023-02-10 5:22 dpdklab
2023-02-10 5:26 dpdklab
2023-02-10 5:28 dpdklab
2023-02-10 5:28 dpdklab
2023-02-11 9:39 dpdklab
2023-02-11 22:39 dpdklab
2023-02-12 3:02 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=202302090122.3191M0283318626@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).