automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125134 [PATCH v1] eventdev/timer: use loop to check for timeout events
Date: Wed, 15 Mar 2023 15:50:25 +0800	[thread overview]
Message-ID: <202303150750.32F7oPHs3289539@localhost.localdomain> (raw)
In-Reply-To: <d7f77765b09c5333df105c317344e983a2f1ad45.1678867113.git.sthotton@marvell.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125134

_Compilation OK_

Submitter: Shijith Thotton <sthotton@marvell.com>
Date: Wed, 15 Mar 2023 13:30:42 +0530
DPDK git baseline: Repo:dpdk-next-eventdev
  Branch: for-main
  CommitID: baf13c3135d0c5998fff7edc23fb89412dc89246

125134 --> 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


       reply	other threads:[~2023-03-15  8:04 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d7f77765b09c5333df105c317344e983a2f1ad45.1678867113.git.sthotton@marvell.com>
2023-03-15  7:50 ` qemudev [this message]
2023-03-15  7:54 ` qemudev
2023-03-15  8:02 ` |WARNING| " checkpatch
2023-03-15 10:19 ` |SUCCESS| " 0-day Robot
2023-03-15  8:34 |SUCCESS| pw125134 [PATCH] [v1] " dpdklab
2023-03-15  8:40 dpdklab
2023-03-15  8:41 dpdklab
2023-03-15  8:45 dpdklab
2023-03-15  8:47 dpdklab
2023-03-15  8:47 dpdklab
2023-03-15  8:48 dpdklab
2023-03-15  8:51 dpdklab
2023-03-15  8:51 dpdklab
2023-03-15  8:52 dpdklab
2023-03-15  8:56 dpdklab
2023-03-15  8:57 dpdklab
2023-03-15  9:00 dpdklab
2023-03-15  9:01 dpdklab
2023-03-15  9:01 dpdklab
2023-03-15  9:01 dpdklab
2023-03-15  9:06 dpdklab
2023-03-15  9:06 dpdklab
2023-03-15  9:07 dpdklab
2023-03-15  9:14 dpdklab
2023-03-15  9:18 dpdklab
2023-03-15  9:18 dpdklab
2023-03-15  9:21 dpdklab
2023-03-15  9:22 dpdklab
2023-03-15  9:26 dpdklab
2023-03-15  9:31 dpdklab
2023-03-15  9:39 dpdklab
2023-03-15  9:54 dpdklab
2023-03-15  9:54 dpdklab
2023-03-15  9:57 dpdklab
2023-03-15 10:01 dpdklab
2023-03-15 10:08 dpdklab
2023-03-17  8:19 dpdklab
2023-03-17 10:34 dpdklab
2023-03-17 11:39 dpdklab
2023-03-17 16:45 dpdklab
2023-03-17 17:00 dpdklab
2023-03-17 17:00 dpdklab
2023-03-17 17:08 dpdklab
2023-03-17 17:09 dpdklab
2023-03-17 17:15 dpdklab
2023-03-17 17:16 dpdklab
2023-03-17 17:30 dpdklab
2023-03-17 17:30 dpdklab
2023-03-17 17:31 dpdklab
2023-03-17 17:33 dpdklab
2023-03-17 17:49 dpdklab
2023-03-17 17:49 dpdklab
2023-03-18  6:23 dpdklab
2023-03-18  6:24 dpdklab
2023-03-18  6:26 dpdklab
2023-03-18  6:27 dpdklab
2023-03-18  6:37 dpdklab
2023-03-18  6:39 dpdklab
2023-03-18  6:40 dpdklab
2023-03-18  6:44 dpdklab
2023-03-18  6:50 dpdklab
2023-03-18  6:56 dpdklab
2023-03-18  6:57 dpdklab
2023-03-18  7:02 dpdklab
2023-03-18  7: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=202303150750.32F7oPHs3289539@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).