From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129921 [PATCH] bus/pci: fix legacy device IO port map in
Date: Sun, 06 Aug 2023 19:34:30 -0700 (PDT) [thread overview]
Message-ID: <64d05836.170a0220.4695f.ce8dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/129921
_Functional Testing PASS_
Submitter: Wenwu Ma <wenwux.ma@intel.com>
Date: Monday, August 07 2023 01:58:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9836014d4c2b1b2c29948c928fd386b2944b6bcf
129921 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-148-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
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/27237/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-07 2:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 2:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-07 3:52 dpdklab
2023-08-07 3:30 dpdklab
2023-08-07 3:14 dpdklab
2023-08-07 3:09 dpdklab
2023-08-07 3:05 dpdklab
2023-08-07 3:05 dpdklab
2023-08-07 3:01 dpdklab
2023-08-07 3:00 dpdklab
2023-08-07 2:55 dpdklab
2023-08-07 2:55 dpdklab
2023-08-07 2:54 dpdklab
2023-08-07 2:51 dpdklab
2023-08-07 2:41 dpdklab
2023-08-07 2:41 dpdklab
2023-08-07 2:39 dpdklab
2023-08-07 2:38 dpdklab
2023-08-07 2:37 dpdklab
2023-08-07 2:35 dpdklab
2023-08-07 2:34 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=64d05836.170a0220.4695f.ce8dSMTPIN_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).