From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124837 [PATCH] doc: fix naming of NVIDIA devices
Date: Wed, 8 Mar 2023 00:40:14 +0000 (UTC) [thread overview]
Message-ID: <20230308004014.11BBF6011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-aarch64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/124837
_Testing PASS_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Tuesday, March 07 2023 15:28:25
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:813d0eead31deb75b774524ad21e99136fbad331
124837 --> 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 |
+-------------------------------+----------------+
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25635/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-08 0:40 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 0:40 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-08 4:59 dpdklab
2023-03-08 4:23 dpdklab
2023-03-08 4:23 dpdklab
2023-03-08 4:05 dpdklab
2023-03-08 3:29 dpdklab
2023-03-08 3:29 dpdklab
2023-03-08 2:38 dpdklab
2023-03-08 2:32 dpdklab
2023-03-08 2:26 dpdklab
2023-03-08 2:03 dpdklab
2023-03-08 1:44 dpdklab
2023-03-08 1:32 dpdklab
2023-03-08 1:14 dpdklab
2023-03-08 1:11 dpdklab
2023-03-08 1:01 dpdklab
2023-03-08 0:59 dpdklab
2023-03-08 0:54 dpdklab
2023-03-08 0:48 dpdklab
2023-03-08 0:48 dpdklab
2023-03-08 0:45 dpdklab
2023-03-08 0:45 dpdklab
2023-03-08 0:42 dpdklab
2023-03-08 0:41 dpdklab
2023-03-08 0:37 dpdklab
2023-03-08 0:36 dpdklab
2023-03-08 0:35 dpdklab
2023-03-08 0:35 dpdklab
2023-03-08 0:28 dpdklab
2023-03-08 0:27 dpdklab
2023-03-08 0:25 dpdklab
2023-03-08 0:25 dpdklab
2023-03-08 0:21 dpdklab
2023-03-08 0:20 dpdklab
2023-03-08 0:19 dpdklab
2023-03-08 0:18 dpdklab
2023-03-08 0:18 dpdklab
2023-03-08 0:15 dpdklab
[not found] <20230307152825.263841-1-thomas@monjalon.net>
2023-03-07 15:17 ` qemudev
2023-03-07 15:21 ` qemudev
2023-03-07 17:39 ` 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=20230308004014.11BBF6011D@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 \
/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).