From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125145 [PATCH v2] vhost: fix madvise IOTLB entries pages overlap check
Date: Wed, 15 Mar 2023 19:32:06 +0800 [thread overview]
Message-ID: <202303151132.32FBW6Dq3558013@localhost.localdomain> (raw)
In-Reply-To: <20230315114010.444005-1-maxime.coquelin@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125145
_Compilation OK_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Wed, 15 Mar 2023 12:40:10 +0100
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: 5d267b5a60fa6a9af64fb76cf36db55bd17ed9bd
125145 --> 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 parent reply other threads:[~2023-03-15 11:46 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230315114010.444005-1-maxime.coquelin@redhat.com>
2023-03-15 11:32 ` qemudev [this message]
2023-03-15 11:36 ` qemudev
2023-03-15 11:41 ` |WARNING| " checkpatch
2023-03-15 13:39 ` |SUCCESS| " 0-day Robot
2023-03-15 12:54 |SUCCESS| pw125145 [PATCH] [v2] " dpdklab
2023-03-15 12:54 dpdklab
2023-03-15 12:59 dpdklab
2023-03-15 12:59 dpdklab
2023-03-15 13:04 dpdklab
2023-03-15 13:04 dpdklab
2023-03-15 13:06 dpdklab
2023-03-15 13:11 dpdklab
2023-03-15 13:15 dpdklab
2023-03-15 13:19 dpdklab
2023-03-15 13:20 dpdklab
2023-03-15 13:25 dpdklab
2023-03-15 13:28 dpdklab
2023-03-15 13:32 dpdklab
2023-03-15 13:38 dpdklab
2023-03-15 13:38 dpdklab
2023-03-15 13:39 dpdklab
2023-03-15 13:41 dpdklab
2023-03-15 13:42 dpdklab
2023-03-15 13:42 dpdklab
2023-03-15 13:47 dpdklab
2023-03-15 13:51 dpdklab
2023-03-15 13:53 dpdklab
2023-03-15 14:05 dpdklab
2023-03-15 14:22 dpdklab
2023-03-15 14:34 dpdklab
2023-03-15 14:36 dpdklab
2023-03-15 14:39 dpdklab
2023-03-15 15:08 dpdklab
2023-03-15 15:47 dpdklab
2023-03-15 16:24 dpdklab
2023-03-15 17:08 dpdklab
2023-03-17 21:50 dpdklab
2023-03-17 23:11 dpdklab
2023-03-19 2:57 dpdklab
2023-03-19 3:36 dpdklab
2023-03-19 3:38 dpdklab
2023-03-19 3:43 dpdklab
2023-03-19 3:46 dpdklab
2023-03-19 3:47 dpdklab
2023-03-19 3:51 dpdklab
2023-03-19 3:53 dpdklab
2023-03-19 3:57 dpdklab
2023-03-19 4:01 dpdklab
2023-03-19 4:04 dpdklab
2023-03-19 4:11 dpdklab
2023-03-19 4:12 dpdklab
2023-03-19 4:16 dpdklab
2023-03-19 4:16 dpdklab
2023-03-19 4:20 dpdklab
2023-03-19 4:28 dpdklab
2023-03-19 4:32 dpdklab
2023-03-19 4:33 dpdklab
2023-03-19 4:38 dpdklab
2023-03-19 4:44 dpdklab
2023-03-19 4:46 dpdklab
2023-03-19 4:48 dpdklab
2023-03-19 4:57 dpdklab
2023-03-19 4:58 dpdklab
2023-03-19 5:02 dpdklab
2023-03-19 5:03 dpdklab
2023-03-19 5:04 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=202303151132.32FBW6Dq3558013@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).