automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137984 [PATCH] vhost: fix vring addr update with vDPA
Date: Tue, 5 Mar 2024 16:54:21 +0800	[thread overview]
Message-ID: <202403050854.4258sL8j1624125@localhost.localdomain> (raw)
In-Reply-To: <20240305091326.2697724-1-david.marchand@redhat.com>

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

_Compilation OK_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Tue,  5 Mar 2024 10:13:25 +0100
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: deedfb86a7a6e10064d3cccd593f62072de96e36

137984 --> 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-03-05  9:19 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240305091326.2697724-1-david.marchand@redhat.com>
2024-03-05  8:54 ` qemudev [this message]
2024-03-05  8:58 ` qemudev
2024-03-05  9:15 ` checkpatch
2024-03-05 10:05 ` 0-day Robot
2024-03-05 10:46 ` |WARNING| " dpdklab
2024-03-05 15:53 ` |SUCCESS| " dpdklab
2024-03-05 16:06 ` dpdklab
2024-03-05 16:06 ` dpdklab
2024-03-05 16:08 ` dpdklab
2024-03-05 16:09 ` dpdklab
2024-03-05 16:10 ` dpdklab
2024-03-05 16:16 ` dpdklab
2024-03-05 16:18 ` dpdklab
2024-03-05 16:31 ` dpdklab
2024-03-05 16:32 ` dpdklab
2024-03-05 16:32 ` dpdklab
2024-03-05 16:32 ` dpdklab
2024-03-05 16:32 ` dpdklab
2024-03-05 16:35 ` dpdklab
2024-03-05 16:39 ` dpdklab
2024-03-05 16:40 ` dpdklab
2024-03-05 16:41 ` dpdklab
2024-03-05 16:41 ` dpdklab
2024-03-05 16:49 ` dpdklab
2024-03-05 18:01 ` dpdklab
2024-03-05 18:01 ` dpdklab
2024-03-05 18:03 ` dpdklab
2024-03-05 18:03 ` dpdklab
2024-03-05 18:04 ` dpdklab
2024-03-05 18:05 ` dpdklab
2024-03-05 18:06 ` dpdklab
2024-03-05 18:16 ` dpdklab
2024-03-05 18:17 ` dpdklab
2024-03-05 18:17 ` dpdklab
2024-03-05 18:23 ` dpdklab
2024-03-05 18:24 ` dpdklab
2024-03-05 19:03 ` dpdklab
2024-03-05 19:05 ` dpdklab
2024-03-05 19:14 ` dpdklab
2024-03-05 19:14 ` dpdklab
2024-03-05 19:15 ` dpdklab
2024-03-05 19:18 ` dpdklab
2024-03-05 19:19 ` dpdklab
2024-03-05 19:20 ` dpdklab
2024-03-05 19:31 ` dpdklab
2024-03-05 19:53 ` dpdklab
2024-03-05 20:21 ` dpdklab
2024-03-09 17:32 ` dpdklab
2024-03-09 18:05 ` 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=202403050854.4258sL8j1624125@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).