automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124886-124888 [PATCH v2 2/2] vhost: refactor to follow new naming convention
Date: Thu, 9 Mar 2023 13:05:54 +0800	[thread overview]
Message-ID: <202303090505.32955sMa1801169@localhost.localdomain> (raw)
In-Reply-To: <20230309051643.70171-3-nmiki@yahoo-corp.jp>

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

_Compilation OK_

Submitter: Nobuhiro MIKI <nmiki@yahoo-corp.jp>
Date: Thu,  9 Mar 2023 14:16:42 +0900
DPDK git baseline: Repo:dpdk-next-virtio
  Branch: main
  CommitID: 1ce8d0c928ec85c9843fe00c1e1397b755ba539e

124886-124888 --> 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-03-09  5:19 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230309051643.70171-3-nmiki@yahoo-corp.jp>
2023-03-09  5:05 ` qemudev [this message]
2023-03-09  5:09 ` qemudev
2023-03-09  5:19 ` |WARNING| pw124888 " checkpatch
2023-03-09  7:59 ` |SUCCESS| " 0-day Robot
2023-03-11  2:46 |SUCCESS| pw124886-124888 [PATCH] [v2, " dpdklab
2023-03-11  2:56 dpdklab
2023-03-11  2:58 dpdklab
2023-03-11  2:58 dpdklab
2023-03-11  3:00 dpdklab
2023-03-11  3:03 dpdklab
2023-03-11  3:06 dpdklab
2023-03-11  3:07 dpdklab
2023-03-11  3:12 dpdklab
2023-03-11  3:15 dpdklab
2023-03-11  3:17 dpdklab
2023-03-11  3:17 dpdklab
2023-03-11  3:18 dpdklab
2023-03-11  3:22 dpdklab
2023-03-11  3:23 dpdklab
2023-03-11  3:28 dpdklab
2023-03-11  3:31 dpdklab
2023-03-11  3:34 dpdklab
2023-03-11  3:36 dpdklab
2023-03-11  3:37 dpdklab
2023-03-11  3:41 dpdklab
2023-03-11  3:44 dpdklab
2023-03-11  3:50 dpdklab
2023-03-11  3:51 dpdklab
2023-03-11  4:04 dpdklab
2023-03-11  4:05 dpdklab
2023-03-11  4:07 dpdklab
2023-03-11  4:17 dpdklab
2023-03-11 22:24 dpdklab
2023-03-11 23:20 dpdklab
2023-03-11 23:22 dpdklab
2023-03-11 23:35 dpdklab
2023-03-12 10:26 dpdklab
2023-03-12 10:29 dpdklab
2023-03-12 10:41 dpdklab
2023-03-12 10:42 dpdklab
2023-03-12 10:44 dpdklab
2023-03-12 10:44 dpdklab
2023-03-12 10:47 dpdklab
2023-03-12 10:48 dpdklab
2023-03-12 10:50 dpdklab
2023-03-12 10:51 dpdklab
2023-03-12 10:53 dpdklab
2023-03-12 11:05 dpdklab
2023-03-12 11:22 dpdklab
2023-03-12 11:26 dpdklab
2023-03-12 11:40 dpdklab
2023-03-12 11:41 dpdklab
2023-03-12 11:47 dpdklab
2023-03-12 11:51 dpdklab
2023-03-12 12:00 dpdklab
2023-03-12 12:03 dpdklab
2023-03-12 12:07 dpdklab
2023-03-12 12:10 dpdklab
2023-03-12 12:15 dpdklab
2023-03-12 12:19 dpdklab
2023-03-12 12:23 dpdklab
2023-03-12 12:25 dpdklab
2023-03-12 12:27 dpdklab
2023-03-12 12:28 dpdklab
2023-03-12 23:03 dpdklab
2023-03-13  0:25 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=202303090505.32955sMa1801169@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).