From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Volodymyr Fialko <vfialko@marvell.com>,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw123582 [PATCH] [v2] bus: fix leak for devices without driver
Date: Sat, 11 Feb 2023 01:57:36 +0000 (UTC) [thread overview]
Message-ID: <20230211015736.2AF6E60098@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/123582
_Testing PASS_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Thursday, February 09 2023 13:22:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a0c837ad1fb5b6a8b10a284ffeb5f9e31bd8ff00
123582 --> testing pass
Test environment and result as below:
+-------------------------------+----------------+
| Environment | dpdk_unit_test |
+===============================+================+
| Ubuntu 20.04 ARM GCC Native | PASS |
+-------------------------------+----------------+
| Ubuntu 20.04 ARM Clang Native | PASS |
+-------------------------------+----------------+
| Windows Server 2019 | PASS |
+-------------------------------+----------------+
| Ubuntu 22.04 | PASS |
+-------------------------------+----------------+
| Debian Bullseye | PASS |
+-------------------------------+----------------+
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: clang 14.0.5-1.fc36
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25319/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-11 1:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 1:57 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-17 7:04 dpdklab
2023-02-12 20:59 dpdklab
2023-02-12 19:13 dpdklab
2023-02-11 2:49 dpdklab
2023-02-11 2:47 dpdklab
2023-02-11 2:45 dpdklab
2023-02-11 2:43 dpdklab
2023-02-11 2:40 dpdklab
2023-02-11 2:24 dpdklab
2023-02-11 2:11 dpdklab
2023-02-11 2:00 dpdklab
2023-02-11 1:54 dpdklab
2023-02-11 1:53 dpdklab
2023-02-11 1:37 dpdklab
2023-02-09 16:30 dpdklab
2023-02-09 14:46 dpdklab
2023-02-09 14:31 dpdklab
2023-02-09 14:26 dpdklab
2023-02-09 14:24 dpdklab
2023-02-09 14:19 dpdklab
2023-02-09 14:15 dpdklab
2023-02-09 14:07 dpdklab
2023-02-09 14:04 dpdklab
2023-02-09 14:02 dpdklab
2023-02-09 13:59 dpdklab
2023-02-09 13:57 dpdklab
2023-02-09 13:57 dpdklab
2023-02-09 13:50 dpdklab
[not found] <20230209132207.1994066-1-vfialko@marvell.com>
2023-02-09 13:12 ` |SUCCESS| pw123582 [PATCH v2] " qemudev
2023-02-09 13:16 ` qemudev
2023-02-09 13:23 ` checkpatch
2023-02-09 14:59 ` 0-day Robot
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=20230211015736.2AF6E60098@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
--cc=vfialko@marvell.com \
/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).