From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138747 [PATCH] dma/cnxk: fix driver header
Date: Fri, 22 Mar 2024 11:33:57 -0700 (PDT) [thread overview]
Message-ID: <65fdcf15.050a0220.d826f.6fafSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240322135255.393511-1-david.marchand@redhat.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138747
_Functional Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Friday, March 22 2024 13:52:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1c3d15933ac525dedfb3f15e7595baccc6d7174d
138747 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29639/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-22 18:33 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240322135255.393511-1-david.marchand@redhat.com>
2024-03-22 13:37 ` qemudev
2024-03-22 13:41 ` qemudev
2024-03-22 13:53 ` checkpatch
2024-03-22 14:45 ` 0-day Robot
2024-03-22 18:20 ` dpdklab
2024-03-22 18:25 ` dpdklab
2024-03-22 18:26 ` dpdklab
2024-03-22 18:27 ` dpdklab
2024-03-22 18:29 ` dpdklab
2024-03-22 18:31 ` dpdklab
2024-03-22 18:32 ` dpdklab
2024-03-22 18:32 ` dpdklab
2024-03-22 18:33 ` dpdklab [this message]
2024-03-22 18:34 ` dpdklab
2024-03-22 18:35 ` dpdklab
2024-03-22 18:43 ` dpdklab
2024-03-22 18:43 ` dpdklab
2024-03-22 18:43 ` dpdklab
2024-03-22 18:43 ` dpdklab
2024-03-22 18:52 ` dpdklab
2024-03-22 18:54 ` dpdklab
2024-03-22 18:57 ` dpdklab
2024-03-22 18:58 ` dpdklab
2024-03-22 18:58 ` dpdklab
2024-03-22 18:59 ` dpdklab
2024-03-22 18:59 ` dpdklab
2024-03-22 19:01 ` dpdklab
2024-03-22 19:09 ` dpdklab
2024-03-22 19:09 ` dpdklab
2024-03-22 19:09 ` dpdklab
2024-03-22 19:09 ` dpdklab
2024-03-22 19:10 ` dpdklab
2024-03-22 19:10 ` dpdklab
2024-03-22 19:10 ` dpdklab
2024-03-22 19:10 ` dpdklab
2024-03-22 19:11 ` dpdklab
2024-03-22 19:11 ` dpdklab
2024-03-22 19:11 ` dpdklab
2024-03-22 19:11 ` dpdklab
2024-03-22 19:12 ` dpdklab
2024-03-22 19:12 ` dpdklab
2024-03-22 19:13 ` dpdklab
2024-03-22 19:13 ` dpdklab
2024-03-22 19:14 ` dpdklab
2024-03-22 19:14 ` dpdklab
2024-03-22 19:15 ` dpdklab
2024-03-22 19:16 ` dpdklab
2024-03-22 19:17 ` dpdklab
2024-03-22 19:18 ` dpdklab
2024-03-22 19:19 ` dpdklab
2024-03-22 19:20 ` dpdklab
2024-03-22 19:21 ` dpdklab
2024-03-22 19:23 ` dpdklab
2024-03-22 19:25 ` dpdklab
2024-03-22 19:26 ` dpdklab
2024-03-22 19:27 ` dpdklab
2024-03-22 19:28 ` dpdklab
2024-03-22 19:29 ` dpdklab
2024-03-22 19:30 ` dpdklab
2024-03-22 19:30 ` dpdklab
2024-03-22 19:32 ` dpdklab
2024-03-22 19:33 ` dpdklab
2024-03-22 19:34 ` dpdklab
2024-03-22 19:34 ` dpdklab
2024-03-22 19:38 ` dpdklab
2024-03-22 19:39 ` dpdklab
2024-03-22 19:40 ` dpdklab
2024-03-22 19:42 ` dpdklab
2024-03-22 19:43 ` dpdklab
2024-03-22 19:45 ` dpdklab
2024-03-22 19:48 ` dpdklab
2024-03-22 19:55 ` dpdklab
2024-03-22 19:56 ` dpdklab
2024-03-22 20:05 ` dpdklab
2024-03-22 20:10 ` dpdklab
2024-03-22 20:16 ` dpdklab
2024-03-22 20:46 ` dpdklab
2024-03-22 20:46 ` dpdklab
2024-03-22 21:48 ` dpdklab
2024-03-24 6:30 ` dpdklab
2024-03-24 7:06 ` 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=65fdcf15.050a0220.d826f.6fafSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).