From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126024 [PATCH] net/virtio-user: fix leak when initialisation fails
Date: Thu, 13 Apr 2023 18:02:10 +0800 [thread overview]
Message-ID: <202304131002.33DA2AkY3133683@localhost.localdomain> (raw)
In-Reply-To: <20230413101041.1638478-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126024
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Thu, 13 Apr 2023 12:10:41 +0200
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: 119a15f4c451282ec799e192b631f3c607a0a509
126024 --> 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-04-13 10:16 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230413101041.1638478-1-david.marchand@redhat.com>
2023-04-13 10:02 ` qemudev [this message]
2023-04-13 10:06 ` qemudev
2023-04-13 10:11 ` checkpatch
2023-04-13 11:39 ` 0-day Robot
2023-04-13 18:37 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-04-13 18:19 dpdklab
2023-04-13 16:47 dpdklab
2023-04-13 16:21 dpdklab
2023-04-13 16:08 dpdklab
2023-04-13 16:04 dpdklab
2023-04-13 16:04 dpdklab
2023-04-13 15:59 dpdklab
2023-04-13 15:57 dpdklab
2023-04-13 15:52 dpdklab
2023-04-13 15:39 dpdklab
2023-04-13 15:38 dpdklab
2023-04-13 15:37 dpdklab
2023-04-13 15:36 dpdklab
2023-04-13 15:34 dpdklab
2023-04-13 15:28 dpdklab
2023-04-13 15:25 dpdklab
2023-04-13 15:24 dpdklab
2023-04-13 15:23 dpdklab
2023-04-13 15:20 dpdklab
2023-04-13 15:19 dpdklab
2023-04-13 15:16 dpdklab
2023-04-13 15:16 dpdklab
2023-04-13 15:11 dpdklab
2023-04-13 15:03 dpdklab
2023-04-13 14:00 dpdklab
2023-04-13 13:59 dpdklab
2023-04-13 13:25 dpdklab
2023-04-13 12:06 dpdklab
2023-04-13 11:59 dpdklab
2023-04-13 11:53 dpdklab
2023-04-13 11:50 dpdklab
2023-04-13 11:46 dpdklab
2023-04-13 11:46 dpdklab
2023-04-13 11:43 dpdklab
2023-04-13 11:42 dpdklab
2023-04-13 11:41 dpdklab
2023-04-13 11:33 dpdklab
2023-04-13 11:31 dpdklab
2023-04-13 11:30 dpdklab
2023-04-13 11:30 dpdklab
2023-04-13 11:29 dpdklab
2023-04-13 11:27 dpdklab
2023-04-13 11:26 dpdklab
2023-04-13 11:25 dpdklab
2023-04-13 11:23 dpdklab
2023-04-13 11:21 dpdklab
2023-04-13 11:21 dpdklab
2023-04-13 11:20 dpdklab
2023-04-13 11:17 dpdklab
2023-04-13 11:16 dpdklab
2023-04-13 11:16 dpdklab
2023-04-13 11:16 dpdklab
2023-04-13 11:15 dpdklab
2023-04-13 11:14 dpdklab
2023-04-13 11:14 dpdklab
2023-04-13 11:13 dpdklab
2023-04-13 11:09 dpdklab
2023-04-13 11:08 dpdklab
2023-04-13 11:07 dpdklab
2023-04-13 11:07 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=202304131002.33DA2AkY3133683@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).