automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125092 [PATCH v2] net/virtio: remove address width limit for modern devices
Date: Wed, 15 Mar 2023 08:49:14 +0800	[thread overview]
Message-ID: <202303150049.32F0nEvh3172431@localhost.localdomain> (raw)
In-Reply-To: <20230314085334.3656447-1-david.marchand@redhat.com>

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

_Compilation OK_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Tue, 14 Mar 2023 09:53:34 +0100
DPDK git baseline: Repo:dpdk-next-virtio
  Branch: main
  CommitID: 5d267b5a60fa6a9af64fb76cf36db55bd17ed9bd

125092 --> 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


  parent reply	other threads:[~2023-03-15  1:03 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230314085334.3656447-1-david.marchand@redhat.com>
2023-03-14  8:54 ` checkpatch
2023-03-14 11:03 ` 0-day Robot
2023-03-15  0:49 ` qemudev [this message]
2023-03-15  0:49 ` qemudev
2023-03-16 11:21 |SUCCESS| pw125092 [PATCH] [v2] " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-03-16 10:03 dpdklab
2023-03-15 15:01 dpdklab
2023-03-15 15:00 dpdklab
2023-03-15 14:21 dpdklab
2023-03-15 14:19 dpdklab
2023-03-15 14:18 dpdklab
2023-03-15 14:08 dpdklab
2023-03-15 14:02 dpdklab
2023-03-15 14:01 dpdklab
2023-03-15 14:00 dpdklab
2023-03-15 13:51 dpdklab
2023-03-15 13:43 dpdklab
2023-03-15 13:43 dpdklab
2023-03-15 13:42 dpdklab
2023-03-15 13:39 dpdklab
2023-03-15 13:39 dpdklab
2023-03-15 13:25 dpdklab
2023-03-15 13:23 dpdklab
2023-03-15 13:19 dpdklab
2023-03-15 13:16 dpdklab
2023-03-15 13:07 dpdklab
2023-03-15 13:01 dpdklab
2023-03-15 12:58 dpdklab
2023-03-15 12:52 dpdklab
2023-03-15 12:51 dpdklab
2023-03-15 12:43 dpdklab
2023-03-15 12:40 dpdklab
2023-03-15 12:33 dpdklab
2023-03-14 21:59 dpdklab
2023-03-14 21:39 dpdklab
2023-03-14 21:22 dpdklab
2023-03-14 21:12 dpdklab
2023-03-14 12:08 dpdklab
2023-03-14 11:49 dpdklab
2023-03-14 11:32 dpdklab
2023-03-14 11:27 dpdklab
2023-03-14 11:22 dpdklab
2023-03-14 11:22 dpdklab
2023-03-14 11:20 dpdklab
2023-03-14 11:18 dpdklab
2023-03-14 11:17 dpdklab
2023-03-14 11:14 dpdklab
2023-03-14 11:13 dpdklab
2023-03-14 11:13 dpdklab
2023-03-14 11:11 dpdklab
2023-03-14 11:06 dpdklab
2023-03-14 11:00 dpdklab
2023-03-14 10:55 dpdklab
2023-03-14 10:50 dpdklab
2023-03-14 10:45 dpdklab
2023-03-14 10:42 dpdklab
2023-03-14 10:42 dpdklab
2023-03-14 10:40 dpdklab
2023-03-14 10:39 dpdklab
2023-03-14 10:37 dpdklab
2023-03-14 10:36 dpdklab
2023-03-14 10:34 dpdklab
2023-03-14 10:28 dpdklab
2023-03-14 10:25 dpdklab
2023-03-14 10:23 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=202303150049.32F0nEvh3172431@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).