From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw126964 [PATCH] [v2] drivers/net/bnx2x : Add experimental 2.5Gbps support for BCM578xx.
Date: Wed, 17 May 2023 18:45:21 -0700 (PDT) [thread overview]
Message-ID: <64658331.9d0a0220.31dde.1f7bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/126964
_Functional Testing PASS_
Submitter: None <julien_dpdk@jaube.fr>
Date: Thursday, May 18 2023 00:01:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a399d7b5a994e335c446d4b15d7622d71dd8848c
126964 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-148-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26275/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-18 1:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 1:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-18 11:42 dpdklab
2023-05-18 11:42 dpdklab
2023-05-18 3:40 dpdklab
2023-05-18 2:59 dpdklab
2023-05-18 2:53 dpdklab
2023-05-18 2:52 dpdklab
2023-05-18 2:47 dpdklab
2023-05-18 2:44 dpdklab
2023-05-18 2:35 dpdklab
2023-05-18 2:30 dpdklab
2023-05-18 2:29 dpdklab
2023-05-18 2:22 dpdklab
2023-05-18 2:10 dpdklab
2023-05-18 2:07 dpdklab
2023-05-18 1:54 dpdklab
2023-05-18 1:50 dpdklab
2023-05-18 1:41 dpdklab
2023-05-18 1:40 dpdklab
2023-05-18 1:36 dpdklab
2023-05-18 1:28 dpdklab
2023-05-18 1:20 dpdklab
2023-05-18 1:07 dpdklab
2023-05-18 1:07 dpdklab
2023-05-18 0:59 dpdklab
2023-05-18 0:59 dpdklab
2023-05-18 0:59 dpdklab
2023-05-18 0:58 dpdklab
2023-05-18 0:53 dpdklab
[not found] <20230518000111.71360-1-julien_dpdk@jaube.fr>
2023-05-17 23:56 ` |SUCCESS| pw126964 [PATCH v2] " qemudev
2023-05-18 0:00 ` qemudev
2023-05-18 1:00 ` 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=64658331.9d0a0220.31dde.1f7bSMTPIN_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).