automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw142096 [PATCH] net/virtio-user: fix control queue allocation for non-vDPA
Date: Thu, 4 Jul 2024 00:00:33 +0800	[thread overview]
Message-ID: <202407031600.463G0X6A3624939@localhost.localdomain> (raw)
In-Reply-To: <20240703162738.283162-1-maxime.coquelin@redhat.com>

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

_Compilation OK_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Wed,  3 Jul 2024 18:27:38 +0200
DPDK git baseline: Repo:dpdk-next-virtio
  Branch: main
  CommitID: 823f43b2c2c2af8bedb3ffaaadb1a41ddbb1e912

142096 --> 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-07-03 16:29 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240703162738.283162-1-maxime.coquelin@redhat.com>
2024-07-03 16:00 ` qemudev [this message]
2024-07-03 16:05 ` qemudev
2024-07-03 16:28 ` checkpatch
2024-07-03 17:24 ` 0-day Robot
2024-07-04  0:30 ` |PENDING| pw142096 [PATCH] net/virtio-user: fix control queue alloca dpdklab
2024-07-04  0:34 ` dpdklab
2024-07-04  0:42 ` |SUCCESS| " dpdklab
2024-07-04  0:48 ` dpdklab
2024-07-04  0:50 ` dpdklab
2024-07-04  1:24 ` dpdklab
2024-07-04  1:32 ` dpdklab
2024-07-04  1:46 ` dpdklab
2024-07-04  2:31 ` |PENDING| " dpdklab
2024-07-04  2:40 ` dpdklab
2024-07-04  2:42 ` dpdklab
2024-07-04  2:46 ` dpdklab
2024-07-04  2:51 ` dpdklab
2024-07-04  2:51 ` dpdklab
2024-07-04  3:01 ` dpdklab
2024-07-04  3:04 ` dpdklab
2024-07-04  3:06 ` dpdklab
2024-07-04  3:08 ` dpdklab
2024-07-04  3:08 ` dpdklab
2024-07-04  3:10 ` dpdklab
2024-07-04  3:13 ` dpdklab
2024-07-04  3:13 ` |SUCCESS| " dpdklab
2024-07-04  3:14 ` |PENDING| " dpdklab
2024-07-04  3:15 ` dpdklab
2024-07-04  3:33 ` |SUCCESS| " dpdklab
2024-07-04  3:34 ` dpdklab
2024-07-04  4:02 ` dpdklab
2024-07-04  4:07 ` dpdklab
2024-07-04  4:12 ` dpdklab
2024-07-04  4:20 ` dpdklab
2024-07-04  4:55 ` dpdklab
2024-07-04 14:44 ` |PENDING| " dpdklab
2024-07-04 14:45 ` dpdklab
2024-07-04 14:46 ` dpdklab
2024-07-04 14:50 ` dpdklab
2024-07-04 14:50 ` dpdklab
2024-07-04 14:51 ` dpdklab
2024-07-04 14:51 ` dpdklab
2024-07-04 14:57 ` dpdklab
2024-07-04 14:58 ` dpdklab
2024-07-04 14:59 ` dpdklab
2024-07-04 15:00 ` dpdklab
2024-07-04 15:03 ` dpdklab
2024-07-04 15:06 ` dpdklab
2024-07-04 15:06 ` dpdklab
2024-07-04 15:35 ` dpdklab
2024-07-04 15:41 ` dpdklab
2024-07-04 15:44 ` dpdklab
2024-07-04 15:49 ` dpdklab
2024-07-04 15:53 ` dpdklab
2024-07-04 15:54 ` dpdklab
2024-07-04 15:55 ` dpdklab
2024-07-04 16:27 ` dpdklab
2024-07-04 16:32 ` dpdklab
2024-07-04 16:40 ` dpdklab
2024-07-04 18:05 ` dpdklab
2024-07-04 18:06 ` dpdklab
2024-07-04 18:13 ` dpdklab
2024-07-04 18:20 ` dpdklab
2024-07-04 18:29 ` dpdklab
2024-07-04 18:43 ` dpdklab
2024-07-04 18:44 ` dpdklab
2024-07-04 18:49 ` dpdklab
2024-07-04 18:51 ` dpdklab
2024-07-04 18:55 ` dpdklab
2024-07-04 18:55 ` dpdklab
2024-07-04 18:56 ` dpdklab
2024-07-04 19:00 ` dpdklab
2024-07-04 19:00 ` dpdklab
2024-07-04 19:01 ` dpdklab
2024-07-04 19:03 ` dpdklab
2024-07-04 19:06 ` dpdklab
2024-07-04 19:06 ` dpdklab
2024-07-04 19:07 ` dpdklab
2024-07-04 19:10 ` dpdklab
2024-07-04 19:14 ` dpdklab
2024-07-04 19:14 ` dpdklab
2024-07-04 19:15 ` dpdklab
2024-07-04 19:18 ` dpdklab
2024-07-04 19:19 ` dpdklab
2024-07-04 19:19 ` dpdklab
2024-07-04 19:20 ` dpdklab
2024-07-04 19:26 ` dpdklab
2024-07-04 19:32 ` dpdklab
2024-07-04 19:33 ` dpdklab
2024-07-04 19:33 ` dpdklab
2024-07-04 19:36 ` |SUCCESS| " dpdklab
2024-07-04 19:36 ` dpdklab
2024-07-04 19:37 ` |PENDING| " dpdklab
2024-07-04 19:39 ` dpdklab
2024-07-04 19:40 ` dpdklab
2024-07-04 19:44 ` |SUCCESS| " dpdklab
2024-07-04 19:45 ` |PENDING| " dpdklab
2024-07-04 19:51 ` dpdklab
2024-07-04 19:55 ` dpdklab
2024-07-04 19:56 ` dpdklab
2024-07-04 19:56 ` dpdklab
2024-07-04 19:57 ` dpdklab
2024-07-04 19:57 ` dpdklab
2024-07-04 19:59 ` dpdklab
2024-07-04 20:00 ` dpdklab
2024-07-04 20:05 ` dpdklab
2024-07-04 20:09 ` dpdklab
2024-07-04 20:09 ` dpdklab
2024-07-04 20:14 ` dpdklab
2024-07-04 20:15 ` dpdklab
2024-07-04 20:20 ` dpdklab
2024-07-04 20:21 ` dpdklab
2024-07-04 20:26 ` |SUCCESS| " dpdklab
2024-07-04 21:36 ` dpdklab
2024-07-05  2:35 ` dpdklab
2024-07-05 14:00 ` dpdklab
2024-07-05 14:50 ` 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=202407031600.463G0X6A3624939@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).