From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124686 [PATCH] vhost: fix vring enable with VDPA
Date: Mon, 6 Mar 2023 15:24:35 +0800 [thread overview]
Message-ID: <202303060724.3267OZ9c3958469@localhost.localdomain> (raw)
In-Reply-To: <20230302094808.1519310-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124686
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Thu, 2 Mar 2023 10:48:08 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124686 --> 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
next prev parent reply other threads:[~2023-03-06 7:38 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230302094808.1519310-1-david.marchand@redhat.com>
2023-03-02 9:48 ` checkpatch
2023-03-02 12:19 ` 0-day Robot
2023-03-06 7:24 ` qemudev [this message]
2023-03-06 7:25 ` qemudev
2023-03-04 11:38 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-04 11:37 dpdklab
2023-03-04 11:31 dpdklab
2023-03-04 11:16 dpdklab
2023-03-04 11:14 dpdklab
2023-03-04 11:13 dpdklab
2023-03-04 11:12 dpdklab
2023-03-04 11:11 dpdklab
2023-03-04 11:10 dpdklab
2023-03-04 11:08 dpdklab
2023-03-04 11:00 dpdklab
2023-03-04 11:00 dpdklab
2023-03-04 10:57 dpdklab
2023-03-04 10:53 dpdklab
2023-03-04 10:53 dpdklab
2023-03-04 10:34 dpdklab
2023-03-04 10:34 dpdklab
2023-03-04 10:29 dpdklab
2023-03-04 10:26 dpdklab
2023-03-04 10:23 dpdklab
2023-03-04 10:21 dpdklab
2023-03-04 10:20 dpdklab
2023-03-04 10:19 dpdklab
2023-03-04 10:19 dpdklab
2023-03-04 10:09 dpdklab
2023-03-04 9:58 dpdklab
2023-03-04 9:56 dpdklab
2023-03-04 9:53 dpdklab
2023-03-03 8:45 dpdklab
2023-03-03 7:54 dpdklab
2023-03-03 2:25 dpdklab
2023-03-03 2:23 dpdklab
2023-03-02 17:36 dpdklab
2023-03-02 16:45 dpdklab
2023-03-02 16:35 dpdklab
2023-03-02 16:33 dpdklab
2023-03-02 16:33 dpdklab
2023-03-02 16:33 dpdklab
2023-03-02 16:29 dpdklab
2023-03-02 16:28 dpdklab
2023-03-02 16:28 dpdklab
2023-03-02 16:25 dpdklab
2023-03-02 16:25 dpdklab
2023-03-02 16:24 dpdklab
2023-03-02 16:17 dpdklab
2023-03-02 16:12 dpdklab
2023-03-02 16:08 dpdklab
2023-03-02 16:00 dpdklab
2023-03-02 16:00 dpdklab
2023-03-02 15:57 dpdklab
2023-03-02 15:54 dpdklab
2023-03-02 15:53 dpdklab
2023-03-02 15:52 dpdklab
2023-03-02 15:52 dpdklab
2023-03-02 15:51 dpdklab
2023-03-02 15:50 dpdklab
2023-03-02 15:41 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=202303060724.3267OZ9c3958469@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).