From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139199 [PATCH v2] latencystats: performance overhaul
Date: Tue, 9 Apr 2024 05:02:52 +0800 [thread overview]
Message-ID: <202404082102.438L2qNR4093193@localhost.localdomain> (raw)
In-Reply-To: <20240408212615.416813-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139199
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 8 Apr 2024 14:26:15 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139199 --> 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-04-08 21:27 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240408212615.416813-1-stephen@networkplumber.org>
2024-04-08 21:02 ` qemudev [this message]
2024-04-08 21:07 ` qemudev
2024-04-08 21:27 ` |WARNING| " checkpatch
2024-04-08 22:24 ` |SUCCESS| " 0-day Robot
2024-04-09 5:52 ` |SUCCESS| pw139199 [PATCH] [v2] " dpdklab
2024-04-09 5:54 ` dpdklab
2024-04-09 5:57 ` dpdklab
2024-04-09 5:58 ` dpdklab
2024-04-09 6:42 ` dpdklab
2024-04-09 6:45 ` dpdklab
2024-04-09 6:46 ` dpdklab
2024-04-09 6:46 ` dpdklab
2024-04-09 6:50 ` dpdklab
2024-04-09 6:55 ` dpdklab
2024-04-09 6:56 ` dpdklab
2024-04-09 6:56 ` dpdklab
2024-04-09 6:56 ` dpdklab
2024-04-09 6:57 ` dpdklab
2024-04-09 7:00 ` dpdklab
2024-04-09 7:09 ` dpdklab
2024-04-09 7:13 ` dpdklab
2024-04-09 7:18 ` dpdklab
2024-04-09 7:24 ` dpdklab
2024-04-09 7:29 ` dpdklab
2024-04-09 7:30 ` dpdklab
2024-04-09 7:33 ` dpdklab
2024-04-09 7:33 ` dpdklab
2024-04-09 7:34 ` dpdklab
2024-04-09 7:43 ` dpdklab
2024-04-09 7:43 ` dpdklab
2024-04-09 7:44 ` dpdklab
2024-04-09 7:46 ` dpdklab
2024-04-09 7:47 ` dpdklab
2024-04-09 8:00 ` dpdklab
2024-04-09 8:20 ` dpdklab
2024-04-09 8:22 ` dpdklab
2024-04-09 8:41 ` dpdklab
2024-04-09 8:42 ` dpdklab
2024-04-09 8:42 ` dpdklab
2024-04-09 8:43 ` dpdklab
2024-04-09 8:45 ` dpdklab
2024-04-09 8:46 ` dpdklab
2024-04-09 8:47 ` dpdklab
2024-04-09 8:48 ` dpdklab
2024-04-09 8:48 ` dpdklab
2024-04-09 8:49 ` dpdklab
2024-04-09 8:50 ` dpdklab
2024-04-09 8:50 ` dpdklab
2024-04-09 8:51 ` dpdklab
2024-04-09 8:51 ` dpdklab
2024-04-09 8:54 ` dpdklab
2024-04-09 8:55 ` dpdklab
2024-04-09 8:56 ` dpdklab
2024-04-09 8:56 ` dpdklab
2024-04-09 8:57 ` dpdklab
2024-04-09 8:57 ` dpdklab
2024-04-09 8:57 ` dpdklab
2024-04-09 8:59 ` dpdklab
2024-04-09 8:59 ` dpdklab
2024-04-09 8:59 ` dpdklab
2024-04-09 9:00 ` dpdklab
2024-04-09 9:00 ` dpdklab
2024-04-09 9:00 ` dpdklab
2024-04-09 9:01 ` dpdklab
2024-04-09 9:02 ` dpdklab
2024-04-09 9:03 ` dpdklab
2024-04-09 9:04 ` dpdklab
2024-04-09 9:04 ` dpdklab
2024-04-09 9:05 ` dpdklab
2024-04-09 9:05 ` dpdklab
2024-04-09 9:07 ` dpdklab
2024-04-09 9:07 ` dpdklab
2024-04-09 9:08 ` dpdklab
2024-04-09 9:08 ` dpdklab
2024-04-09 9:09 ` dpdklab
2024-04-09 9:09 ` dpdklab
2024-04-09 9:14 ` dpdklab
2024-04-09 9:34 ` dpdklab
2024-04-09 9:50 ` dpdklab
2024-04-09 9:54 ` dpdklab
2024-04-09 9:57 ` dpdklab
2024-04-09 9:58 ` dpdklab
2024-04-09 10:02 ` dpdklab
2024-04-09 10:16 ` dpdklab
2024-04-09 10:17 ` dpdklab
2024-04-09 10:17 ` dpdklab
2024-04-09 10:53 ` dpdklab
2024-04-09 10:59 ` dpdklab
2024-04-09 14:54 ` 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=202404082102.438L2qNR4093193@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).