automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw142894 [PATCH] net/virtio-user: reset used index counter in dev reset
Date: Mon, 5 Aug 2024 17:42:41 +0800	[thread overview]
Message-ID: <202408050942.4759gfuD1736389@localhost.localdomain> (raw)
In-Reply-To: <20240805100841.276796-1-kshankar@marvell.com>

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

_Compilation OK_

Submitter: Kommula Shiva Shankar <kshankar@marvell.com>
Date: Mon, 5 Aug 2024 10:08:41 +0000
DPDK git baseline: Repo:dpdk-next-virtio
  Branch: main
  CommitID: 9cbdb606e5d04de04be3d9f70f0e76551e8c9a36

142894 --> 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:[~2024-08-05 10:11 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240805100841.276796-1-kshankar@marvell.com>
2024-08-05  9:42 ` qemudev [this message]
2024-08-05  9:47 ` qemudev
2024-08-05 10:09 ` checkpatch
2024-08-05 10:37 ` |SUCCESS| pw142894 [PATCH] net/virtio-user: reset used index counter dpdklab
2024-08-05 10:40 ` |PENDING| " dpdklab
2024-08-05 10:41 ` |SUCCESS| " dpdklab
2024-08-05 10:42 ` |PENDING| " dpdklab
2024-08-05 10:42 ` |SUCCESS| " dpdklab
2024-08-05 10:42 ` dpdklab
2024-08-05 10:43 ` |PENDING| " dpdklab
2024-08-05 10:43 ` dpdklab
2024-08-05 10:43 ` |SUCCESS| " dpdklab
2024-08-05 10:43 ` |PENDING| " dpdklab
2024-08-05 10:45 ` dpdklab
2024-08-05 10:46 ` dpdklab
2024-08-05 10:46 ` dpdklab
2024-08-05 10:49 ` |SUCCESS| " dpdklab
2024-08-05 10:54 ` |PENDING| " dpdklab
2024-08-05 10:55 ` dpdklab
2024-08-05 10:56 ` dpdklab
2024-08-05 10:56 ` dpdklab
2024-08-05 10:56 ` dpdklab
2024-08-05 10:57 ` dpdklab
2024-08-05 10:57 ` dpdklab
2024-08-05 10:57 ` dpdklab
2024-08-05 10:57 ` dpdklab
2024-08-05 10:57 ` dpdklab
2024-08-05 10:58 ` dpdklab
2024-08-05 10:58 ` dpdklab
2024-08-05 10:58 ` dpdklab
2024-08-05 10:58 ` dpdklab
2024-08-05 10:58 ` |SUCCESS| " dpdklab
2024-08-05 11:00 ` |PENDING| " dpdklab
2024-08-05 11:02 ` |SUCCESS| " dpdklab
2024-08-05 11:02 ` dpdklab
2024-08-05 11:02 ` |SUCCESS| pw142894 [PATCH] net/virtio-user: reset used index counter in dev reset 0-day Robot
2024-08-05 11:03 ` |PENDING| pw142894 [PATCH] net/virtio-user: reset used index counter dpdklab
2024-08-05 11:05 ` dpdklab
2024-08-05 11:05 ` dpdklab
2024-08-05 11:05 ` dpdklab
2024-08-05 11:05 ` |SUCCESS| " dpdklab
2024-08-05 11:05 ` |PENDING| " dpdklab
2024-08-05 11:05 ` dpdklab
2024-08-05 11:08 ` dpdklab
2024-08-05 11:08 ` dpdklab
2024-08-05 11:09 ` dpdklab
2024-08-05 11:10 ` dpdklab
2024-08-05 11:11 ` dpdklab
2024-08-05 11:11 ` dpdklab
2024-08-05 11:17 ` dpdklab
2024-08-05 11:17 ` dpdklab
2024-08-05 11:17 ` dpdklab
2024-08-05 11:20 ` dpdklab
2024-08-05 11:24 ` dpdklab
2024-08-05 11:24 ` dpdklab
2024-08-05 11:25 ` |SUCCESS| " dpdklab
2024-08-05 11:25 ` |PENDING| " dpdklab
2024-08-05 11:26 ` dpdklab
2024-08-05 11:26 ` dpdklab
2024-08-05 11:28 ` dpdklab
2024-08-05 11:29 ` dpdklab
2024-08-05 11:30 ` dpdklab
2024-08-05 11:31 ` |SUCCESS| " dpdklab
2024-08-05 11:31 ` |PENDING| " dpdklab
2024-08-05 11:32 ` dpdklab
2024-08-05 11:34 ` |SUCCESS| " dpdklab
2024-08-05 11:38 ` |PENDING| " dpdklab
2024-08-05 11:39 ` dpdklab
2024-08-05 11:39 ` dpdklab
2024-08-05 11:39 ` dpdklab
2024-08-05 11:40 ` dpdklab
2024-08-05 11:41 ` dpdklab
2024-08-05 11:42 ` dpdklab
2024-08-05 11:43 ` dpdklab
2024-08-05 11:45 ` dpdklab
2024-08-05 11:46 ` dpdklab
2024-08-05 11:47 ` dpdklab
2024-08-05 11:48 ` dpdklab
2024-08-05 11:49 ` dpdklab
2024-08-05 11:49 ` dpdklab
2024-08-05 11:51 ` dpdklab
2024-08-05 11:51 ` dpdklab
2024-08-05 11:53 ` dpdklab
2024-08-05 11:54 ` dpdklab
2024-08-05 11:56 ` dpdklab
2024-08-05 11:56 ` dpdklab
2024-08-05 11:57 ` dpdklab
2024-08-05 11:58 ` dpdklab
2024-08-05 11:58 ` dpdklab
2024-08-05 11:59 ` |SUCCESS| " dpdklab
2024-08-05 12:02 ` dpdklab
2024-08-05 12:05 ` |PENDING| " dpdklab
2024-08-05 12:06 ` dpdklab
2024-08-05 12:08 ` dpdklab
2024-08-05 12:10 ` dpdklab
2024-08-05 12:13 ` dpdklab
2024-08-05 12:14 ` |SUCCESS| " dpdklab
2024-08-05 12:15 ` |PENDING| " dpdklab
2024-08-05 12:17 ` dpdklab
2024-08-05 12:17 ` dpdklab
2024-08-05 12:18 ` dpdklab
2024-08-05 12:21 ` dpdklab
2024-08-05 12:25 ` dpdklab
2024-08-05 12:28 ` dpdklab
2024-08-05 12:29 ` dpdklab
2024-08-05 12:30 ` |SUCCESS| " dpdklab
2024-08-05 12:31 ` dpdklab
2024-08-06 20:57 ` dpdklab
2024-08-06 21:06 ` dpdklab
2024-08-06 21:16 ` 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=202408050942.4759gfuD1736389@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).