From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124555 [PATCH] vhost: fix OOB access for invalid vid
Date: Wed, 1 Mar 2023 16:22:24 +0800 [thread overview]
Message-ID: <202303010822.3218MO5q953438@localhost.localdomain> (raw)
In-Reply-To: <20230227105927.3643421-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124555
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Mon, 27 Feb 2023 11:59:27 +0100
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: fe2c18a0a8b22703dec3add385a371ad819d7872
124555 --> 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-01 8:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230227105927.3643421-1-david.marchand@redhat.com>
2023-02-27 11:00 ` checkpatch
2023-02-27 13:19 ` 0-day Robot
2023-03-01 8:22 ` qemudev [this message]
2023-03-01 8:22 ` qemudev
2023-02-27 23:39 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-27 22:54 dpdklab
2023-02-27 21:05 dpdklab
2023-02-27 21:04 dpdklab
2023-02-27 21:03 dpdklab
2023-02-27 21:01 dpdklab
2023-02-27 20:54 dpdklab
2023-02-27 20:52 dpdklab
2023-02-27 20:51 dpdklab
2023-02-27 20:50 dpdklab
2023-02-27 20:49 dpdklab
2023-02-27 20:42 dpdklab
2023-02-27 20:40 dpdklab
2023-02-27 20:27 dpdklab
2023-02-27 20:24 dpdklab
2023-02-27 17:48 dpdklab
2023-02-27 17:08 dpdklab
2023-02-27 16:21 dpdklab
2023-02-27 16:13 dpdklab
2023-02-27 16:12 dpdklab
2023-02-27 16:09 dpdklab
2023-02-27 16:05 dpdklab
2023-02-27 16:05 dpdklab
2023-02-27 16:01 dpdklab
2023-02-27 15:59 dpdklab
2023-02-27 15:51 dpdklab
2023-02-27 15:49 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=202303010822.3218MO5q953438@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).