From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125971 [PATCH] eventdev/timer: move buffer flush call
Date: Thu, 13 Apr 2023 03:47:07 +0800 [thread overview]
Message-ID: <202304121947.33CJl74A2077426@localhost.localdomain> (raw)
In-Reply-To: <20230412195637.450033-1-erik.g.carrillo@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125971
_Compilation OK_
Submitter: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
Date: Wed, 12 Apr 2023 14:56:37 -0500
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: bcf10f89acb577b7d742dddd5f02b0b464c4b598
125971 --> 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-04-12 20:01 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230412195637.450033-1-erik.g.carrillo@intel.com>
2023-04-12 19:47 ` qemudev [this message]
2023-04-12 19:51 ` qemudev
2023-04-12 19:57 ` |WARNING| " checkpatch
2023-04-12 21:18 ` |SUCCESS| " 0-day Robot
2023-04-12 22:10 dpdklab
2023-04-12 22:17 dpdklab
2023-04-12 22:17 dpdklab
2023-04-12 22:18 dpdklab
2023-04-12 22:19 dpdklab
2023-04-12 22:20 dpdklab
2023-04-12 22:27 dpdklab
2023-04-12 22:28 dpdklab
2023-04-12 22:30 dpdklab
2023-04-12 22:30 dpdklab
2023-04-12 22:34 dpdklab
2023-04-12 22:40 dpdklab
2023-04-12 22:43 dpdklab
2023-04-12 22:44 dpdklab
2023-04-12 22:51 dpdklab
2023-04-12 22:53 dpdklab
2023-04-12 23:00 dpdklab
2023-04-12 23:13 dpdklab
2023-04-12 23:13 dpdklab
2023-04-12 23:26 dpdklab
2023-04-13 0:01 dpdklab
2023-04-13 0:25 dpdklab
2023-04-13 0:28 dpdklab
2023-04-13 0:31 dpdklab
2023-04-13 0:34 dpdklab
2023-04-13 0:50 dpdklab
2023-04-13 0:55 dpdklab
2023-04-13 0:57 dpdklab
2023-04-13 0:59 dpdklab
2023-04-13 1:02 dpdklab
2023-04-13 1:04 dpdklab
2023-04-13 1:05 dpdklab
2023-04-13 1:10 dpdklab
2023-04-13 1:12 dpdklab
2023-04-13 1:13 dpdklab
2023-04-13 1:21 dpdklab
2023-04-13 1:22 dpdklab
2023-04-13 1:22 dpdklab
2023-04-13 1:25 dpdklab
2023-04-13 1:28 dpdklab
2023-04-13 1:31 dpdklab
2023-04-13 1:37 dpdklab
2023-04-13 1:37 dpdklab
2023-04-13 1:56 dpdklab
2023-04-13 2:01 dpdklab
2023-04-13 2:06 dpdklab
2023-04-13 2:10 dpdklab
2023-04-13 2:26 dpdklab
2023-04-13 2:30 dpdklab
2023-04-13 4:16 dpdklab
2023-04-13 4:16 dpdklab
2023-04-13 5:26 dpdklab
2023-04-13 5:26 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=202304121947.33CJl74A2077426@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).