automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133267 [PATCH] vhost: make experimental API's stable
Date: Wed, 25 Oct 2023 00:12:08 +0800	[thread overview]
Message-ID: <202310241612.39OGC8v22448810@localhost.localdomain> (raw)
In-Reply-To: <20231024163123.12576-1-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 24 Oct 2023 09:31:23 -0700
DPDK git baseline: Repo:dpdk-next-virtio
  Branch: main
  CommitID: 0ba46799cfb4667d5d7cf81c2d297c0771cb7cd1

133267 --> 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-10-24 16:33 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231024163123.12576-1-stephen@networkplumber.org>
2023-10-24 16:12 ` qemudev [this message]
2023-10-24 16:16 ` qemudev
2023-10-24 16:32 ` |WARNING| " checkpatch
2023-10-24 17:39 ` |SUCCESS| " 0-day Robot
2023-10-24 17:09 dpdklab
2023-10-24 17:10 dpdklab
2023-10-24 17:10 dpdklab
2023-10-24 17:11 dpdklab
2023-10-24 17:11 dpdklab
2023-10-24 17:11 dpdklab
2023-10-24 17:12 dpdklab
2023-10-24 17:12 dpdklab
2023-10-24 17:12 dpdklab
2023-10-24 17:12 dpdklab
2023-10-24 17:12 dpdklab
2023-10-24 17:12 dpdklab
2023-10-24 17:13 dpdklab
2023-10-24 17:13 dpdklab
2023-10-24 17:13 dpdklab
2023-10-24 17:13 dpdklab
2023-10-24 17:13 dpdklab
2023-10-24 17:14 dpdklab
2023-10-24 17:14 dpdklab
2023-10-24 17:14 dpdklab
2023-10-24 17:14 dpdklab
2023-10-24 17:15 dpdklab
2023-10-24 17:15 dpdklab
2023-10-24 17:15 dpdklab
2023-10-24 17:15 dpdklab
2023-10-24 17:16 dpdklab
2023-10-24 17:16 dpdklab
2023-10-24 17:17 dpdklab
2023-10-24 17:17 dpdklab
2023-10-24 17:18 dpdklab
2023-10-24 17:18 dpdklab
2023-10-24 17:18 dpdklab
2023-10-24 17:18 dpdklab
2023-10-24 17:18 dpdklab
2023-10-24 17:18 dpdklab
2023-10-24 17:19 dpdklab
2023-10-24 17:19 dpdklab
2023-10-24 17:19 dpdklab
2023-10-24 17:19 dpdklab
2023-10-24 17:19 dpdklab
2023-10-24 17:20 dpdklab
2023-10-24 17:20 dpdklab
2023-10-24 17:21 dpdklab
2023-10-24 17:22 dpdklab
2023-10-24 17:23 dpdklab
2023-10-24 17:23 dpdklab
2023-10-24 17:24 dpdklab
2023-10-24 17:24 dpdklab
2023-10-24 17:26 dpdklab
2023-10-24 17:27 dpdklab
2023-10-24 17:32 dpdklab
2023-10-24 17:35 dpdklab
2023-10-24 18:35 dpdklab
2023-10-25 17: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=202310241612.39OGC8v22448810@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).