From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125089 [PATCH v1] common/cnxk: fix initialization of timer LF count
Date: Wed, 15 Mar 2023 08:51:21 +0800 [thread overview]
Message-ID: <202303150051.32F0pLQY3172647@localhost.localdomain> (raw)
In-Reply-To: <e25bb2c73d173211c49616b37d4fa344ceb7d360.1678765587.git.sthotton@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125089
_Compilation OK_
Submitter: Shijith Thotton <sthotton@marvell.com>
Date: Tue, 14 Mar 2023 09:16:59 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: baf13c3135d0c5998fff7edc23fb89412dc89246
125089 --> 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 prev parent reply other threads:[~2023-03-15 1:05 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e25bb2c73d173211c49616b37d4fa344ceb7d360.1678765587.git.sthotton@marvell.com>
2023-03-14 3:48 ` |WARNING| " checkpatch
2023-03-14 5:59 ` |FAILURE| " 0-day Robot
2023-03-15 0:51 ` qemudev [this message]
2023-03-15 0:51 ` |SUCCESS| " qemudev
2023-03-16 6:46 |SUCCESS| pw125089 [PATCH] [v1] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-16 5:26 dpdklab
2023-03-15 9:58 dpdklab
2023-03-15 9:57 dpdklab
2023-03-15 9:37 dpdklab
2023-03-15 9:35 dpdklab
2023-03-15 9:35 dpdklab
2023-03-15 9:34 dpdklab
2023-03-15 9:20 dpdklab
2023-03-15 9:18 dpdklab
2023-03-15 9:16 dpdklab
2023-03-15 9:10 dpdklab
2023-03-15 9:02 dpdklab
2023-03-15 9:02 dpdklab
2023-03-15 9:01 dpdklab
2023-03-15 9:01 dpdklab
2023-03-15 8:58 dpdklab
2023-03-15 8:53 dpdklab
2023-03-15 8:46 dpdklab
2023-03-15 8:46 dpdklab
2023-03-15 8:43 dpdklab
2023-03-15 8:38 dpdklab
2023-03-15 8:27 dpdklab
2023-03-15 8:25 dpdklab
2023-03-15 8:23 dpdklab
2023-03-15 8:12 dpdklab
2023-03-15 8:07 dpdklab
2023-03-14 21:03 dpdklab
2023-03-14 18:53 dpdklab
2023-03-14 18:46 dpdklab
2023-03-14 17:35 dpdklab
2023-03-14 8:58 dpdklab
2023-03-14 8:56 dpdklab
2023-03-14 8:05 dpdklab
2023-03-14 7:54 dpdklab
2023-03-14 7:52 dpdklab
2023-03-14 7:49 dpdklab
2023-03-14 7:46 dpdklab
2023-03-14 7:45 dpdklab
2023-03-14 7:44 dpdklab
2023-03-14 7:41 dpdklab
2023-03-14 7:39 dpdklab
2023-03-14 7:39 dpdklab
2023-03-14 7:37 dpdklab
2023-03-14 7:36 dpdklab
2023-03-14 7:31 dpdklab
2023-03-14 7:26 dpdklab
2023-03-14 7:14 dpdklab
2023-03-14 7:11 dpdklab
2023-03-14 7:08 dpdklab
2023-03-14 7:07 dpdklab
2023-03-14 7:04 dpdklab
2023-03-14 7:03 dpdklab
2023-03-14 7:01 dpdklab
2023-03-14 7:00 dpdklab
2023-03-14 6:58 dpdklab
2023-03-14 6:52 dpdklab
2023-03-14 6:50 dpdklab
2023-03-14 6:48 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=202303150051.32F0pLQY3172647@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).