automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126165-126164 [PATCH next 7/7] vmxnet3: update to version 7
Date: Mon, 17 Apr 2023 16:07:19 +0800	[thread overview]
Message-ID: <202304170807.33H87Jif1519365@localhost.localdomain> (raw)
In-Reply-To: <20230412162636.30843-8-doshir@vmware.com>

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

_Compilation OK_

Submitter: Ronak Doshi <doshir@vmware.com>
Date: Wed, 12 Apr 2023 09:26:30 -0700
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 40a62da00b3619ed72be6ceeded89d1fe62ed027

126165-126164 --> 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-04-17  8:21 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230412162636.30843-8-doshir@vmware.com>
2023-04-17  8:07 ` qemudev [this message]
2023-04-17  8:11 ` qemudev
2023-04-17  8:16 ` |SUCCESS| pw126164 " checkpatch
2023-04-17 13:51 |SUCCESS| pw126165-126164 [PATCH] [next, " dpdklab
2023-04-17 13:51 dpdklab
2023-04-17 13:56 dpdklab
2023-04-17 13:57 dpdklab
2023-04-17 13:57 dpdklab
2023-04-17 13:59 dpdklab
2023-04-17 13:59 dpdklab
2023-04-17 14:01 dpdklab
2023-04-17 14:02 dpdklab
2023-04-17 14:03 dpdklab
2023-04-17 14:06 dpdklab
2023-04-17 14:11 dpdklab
2023-04-17 14:14 dpdklab
2023-04-17 14:44 dpdklab
2023-04-17 14:46 dpdklab
2023-04-17 14:48 dpdklab
2023-04-17 14:49 dpdklab
2023-04-17 14:50 dpdklab
2023-04-17 14:51 dpdklab
2023-04-17 14:53 dpdklab
2023-04-17 14:54 dpdklab
2023-04-17 15:01 dpdklab
2023-04-17 15:08 dpdklab
2023-04-17 15:25 dpdklab
2023-04-17 15:41 dpdklab
2023-04-17 15:43 dpdklab
2023-04-17 15:50 dpdklab
2023-04-17 15:52 dpdklab
2023-04-17 15:58 dpdklab
2023-04-17 16:00 dpdklab
2023-04-17 16:16 dpdklab
2023-04-17 16:23 dpdklab
2023-04-17 16:40 dpdklab
2023-04-17 16:43 dpdklab
2023-04-17 16:47 dpdklab
2023-04-17 16:47 dpdklab
2023-04-17 16:52 dpdklab
2023-04-17 16:53 dpdklab
2023-04-17 17:01 dpdklab
2023-04-17 17:11 dpdklab
2023-04-17 18:03 dpdklab
2023-04-17 18:03 dpdklab
2023-04-17 19:45 dpdklab
2023-04-17 19:45 dpdklab
2023-04-17 19:49 dpdklab
2023-04-17 20:10 dpdklab
2023-04-17 21:00 dpdklab
2023-04-17 21:48 dpdklab
2023-04-17 21:58 dpdklab
2023-04-17 21:58 dpdklab
2023-04-18 15:16 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=202304170807.33H87Jif1519365@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).