From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123582 [PATCH v2] bus: fix leak for devices without driver
Date: Thu, 9 Feb 2023 21:12:18 +0800 [thread overview]
Message-ID: <202302091312.319DCI2b423118@localhost.localdomain> (raw)
In-Reply-To: <20230209132207.1994066-1-vfialko@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123582
_Compilation OK_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Thu, 9 Feb 2023 14:22:07 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 71a71b18253846547c5e170940fba14544d1461c
123582 --> 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-02-09 13:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230209132207.1994066-1-vfialko@marvell.com>
2023-02-09 13:12 ` qemudev [this message]
2023-02-09 13:16 ` qemudev
2023-02-09 13:23 ` checkpatch
2023-02-09 14:59 ` 0-day Robot
2023-02-09 13:50 |SUCCESS| pw123582 [PATCH] [v2] " dpdklab
2023-02-09 13:57 dpdklab
2023-02-09 13:57 dpdklab
2023-02-09 13:59 dpdklab
2023-02-09 14:02 dpdklab
2023-02-09 14:04 dpdklab
2023-02-09 14:07 dpdklab
2023-02-09 14:15 dpdklab
2023-02-09 14:19 dpdklab
2023-02-09 14:24 dpdklab
2023-02-09 14:26 dpdklab
2023-02-09 14:31 dpdklab
2023-02-09 14:46 dpdklab
2023-02-09 16:30 dpdklab
2023-02-11 1:37 dpdklab
2023-02-11 1:53 dpdklab
2023-02-11 1:54 dpdklab
2023-02-11 1:57 dpdklab
2023-02-11 2:00 dpdklab
2023-02-11 2:11 dpdklab
2023-02-11 2:24 dpdklab
2023-02-11 2:40 dpdklab
2023-02-11 2:43 dpdklab
2023-02-11 2:45 dpdklab
2023-02-11 2:47 dpdklab
2023-02-11 2:49 dpdklab
2023-02-12 19:13 dpdklab
2023-02-12 20:59 dpdklab
2023-02-17 7: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=202302091312.319DCI2b423118@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).