automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122352-122351 [PATCH 2/2] net/vhost: support private dump
Date: Thu, 19 Jan 2023 20:30:09 +0800	[thread overview]
Message-ID: <202301191230.30JCU9SI2813150@localhost.localdomain> (raw)
In-Reply-To: <20230119123056.14338-3-fengchengwen@huawei.com>

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

_Compilation OK_

Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Thu, 19 Jan 2023 12:30:55 +0000
DPDK git baseline: Repo:dpdk-next-virtio
  Branch: main
  CommitID: fe2c18a0a8b22703dec3add385a371ad819d7872

122352-122351 --> 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-01-19 12:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230119123056.14338-3-fengchengwen@huawei.com>
2023-01-19 12:30 ` qemudev [this message]
2023-01-19 12:34 ` qemudev
2023-01-19 12:38 ` |WARNING| pw122351 " checkpatch
2023-01-19 14:19 ` |SUCCESS| " 0-day Robot
2023-01-19 13:12 |SUCCESS| pw122352-122351 [PATCH] [2/2] " dpdklab
2023-01-19 13:13 dpdklab
2023-01-19 13:18 dpdklab
2023-01-19 13:18 dpdklab
2023-01-19 13:20 dpdklab
2023-01-19 13:27 dpdklab
2023-01-19 13:32 dpdklab
2023-01-19 15:57 dpdklab
2023-01-19 19:17 dpdklab
2023-01-19 23:42 dpdklab
2023-01-19 23:51 dpdklab
2023-01-20  0:00 dpdklab
2023-01-20  0:00 dpdklab
2023-01-20  0:00 dpdklab
2023-01-20  0:01 dpdklab
2023-01-20  0:01 dpdklab
2023-01-20  0:05 dpdklab
2023-01-20  0:05 dpdklab
2023-01-20  5:42 dpdklab
2023-01-20 11:20 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=202301191230.30JCU9SI2813150@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).