From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139379 [PATCH] latencystats: fix missing f suffix on literal float
Date: Tue, 16 Apr 2024 05:11:08 +0800 [thread overview]
Message-ID: <202404152111.43FLB8gW1874062@localhost.localdomain> (raw)
In-Reply-To: <1713216746-25584-1-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139379
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Mon, 15 Apr 2024 14:32:26 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139379 --> 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-15 21:36 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1713216746-25584-1-git-send-email-roretzla@linux.microsoft.com>
2024-04-15 21:11 ` qemudev [this message]
2024-04-15 21:15 ` qemudev
2024-04-15 21:33 ` checkpatch
2024-04-15 22:24 ` 0-day Robot
2024-04-16 0:29 ` |SUCCESS| pw139379 [PATCH] latencystats: fix missing f suffix on lit dpdklab
2024-04-16 0:30 ` dpdklab
2024-04-16 0:32 ` dpdklab
2024-04-16 0:33 ` dpdklab
2024-04-16 0:34 ` dpdklab
2024-04-16 0:34 ` dpdklab
2024-04-16 0:35 ` dpdklab
2024-04-16 0:35 ` dpdklab
2024-04-16 0:35 ` dpdklab
2024-04-16 0:36 ` dpdklab
2024-04-16 0:40 ` dpdklab
2024-04-16 0:54 ` dpdklab
2024-04-16 1:03 ` dpdklab
2024-04-16 1:04 ` dpdklab
2024-04-16 1:04 ` dpdklab
2024-04-16 1:04 ` dpdklab
2024-04-16 1:05 ` dpdklab
2024-04-16 1:05 ` dpdklab
2024-04-16 1:05 ` dpdklab
2024-04-16 1:06 ` dpdklab
2024-04-16 1:06 ` dpdklab
2024-04-16 1:06 ` dpdklab
2024-04-16 1:06 ` dpdklab
2024-04-16 1:07 ` dpdklab
2024-04-16 1:07 ` dpdklab
2024-04-16 1:07 ` dpdklab
2024-04-16 1:07 ` dpdklab
2024-04-16 1:07 ` dpdklab
2024-04-16 1:07 ` dpdklab
2024-04-16 1:07 ` dpdklab
2024-04-16 1:08 ` dpdklab
2024-04-16 1:09 ` dpdklab
2024-04-16 1:13 ` dpdklab
2024-04-16 1:14 ` dpdklab
2024-04-16 1:14 ` dpdklab
2024-04-16 1:16 ` dpdklab
2024-04-16 1:18 ` dpdklab
2024-04-16 1:18 ` dpdklab
2024-04-16 1:18 ` dpdklab
2024-04-16 1:18 ` dpdklab
2024-04-16 1:19 ` dpdklab
2024-04-16 1:19 ` dpdklab
2024-04-16 1:19 ` dpdklab
2024-04-16 1:19 ` dpdklab
2024-04-16 1:20 ` dpdklab
2024-04-16 1:21 ` dpdklab
2024-04-16 1:22 ` dpdklab
2024-04-16 1:22 ` dpdklab
2024-04-16 1:22 ` dpdklab
2024-04-16 1:23 ` dpdklab
2024-04-16 1:24 ` dpdklab
2024-04-16 1:29 ` dpdklab
2024-04-16 1:29 ` dpdklab
2024-04-16 1:29 ` dpdklab
2024-04-16 1:30 ` dpdklab
2024-04-16 1:30 ` dpdklab
2024-04-16 1:30 ` dpdklab
2024-04-16 1:30 ` dpdklab
2024-04-16 1:31 ` dpdklab
2024-04-16 1:31 ` dpdklab
2024-04-16 1:32 ` dpdklab
2024-04-16 1:32 ` dpdklab
2024-04-16 1:32 ` dpdklab
2024-04-16 1:33 ` dpdklab
2024-04-16 1:33 ` dpdklab
2024-04-16 1:33 ` dpdklab
2024-04-16 1:34 ` dpdklab
2024-04-16 1:34 ` dpdklab
2024-04-16 1:35 ` dpdklab
2024-04-16 1:35 ` dpdklab
2024-04-16 1:55 ` dpdklab
2024-04-16 1:55 ` dpdklab
2024-04-16 1:55 ` dpdklab
2024-04-16 1:56 ` dpdklab
2024-04-16 1:57 ` dpdklab
2024-04-16 1:57 ` dpdklab
2024-04-16 1:58 ` dpdklab
2024-04-16 1:59 ` dpdklab
2024-04-16 2:00 ` dpdklab
2024-04-16 2:01 ` dpdklab
2024-04-16 2:05 ` dpdklab
2024-04-16 2:06 ` dpdklab
2024-04-16 2:19 ` dpdklab
2024-04-16 2:31 ` dpdklab
2024-04-16 3:40 ` 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=202404152111.43FLB8gW1874062@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).