From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122604-122605 [PATCH v2 2/2] vhost: fix possible FD leaks on MSG_TRUNC and MSG_CTRUNC
Date: Sat, 28 Jan 2023 00:52:02 +0800 [thread overview]
Message-ID: <202301271652.30RGq2aV1870235@localhost.localdomain> (raw)
In-Reply-To: <20230127165540.37863-3-maxime.coquelin@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122605
_Compilation OK_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Fri, 27 Jan 2023 17:55:38 +0100
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: fe2c18a0a8b22703dec3add385a371ad819d7872
122604-122605 --> 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-01-27 17:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230127165540.37863-3-maxime.coquelin@redhat.com>
2023-01-27 16:52 ` qemudev [this message]
2023-01-27 16:55 ` qemudev
2023-01-27 16:56 ` |SUCCESS| pw122605 " checkpatch
2023-01-27 17:39 ` 0-day Robot
2023-01-28 4:30 |SUCCESS| pw122604-122605 [PATCH] [v2, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-01-28 0:02 dpdklab
2023-01-27 22:50 dpdklab
2023-01-27 20:34 dpdklab
2023-01-27 20:34 dpdklab
2023-01-27 20:34 dpdklab
2023-01-27 19:39 dpdklab
2023-01-27 17:41 dpdklab
2023-01-27 17:37 dpdklab
2023-01-27 17:30 dpdklab
2023-01-27 17:27 dpdklab
2023-01-27 17:25 dpdklab
2023-01-27 17:21 dpdklab
2023-01-27 17:21 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=202301271652.30RGq2aV1870235@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).