From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw127953 [PATCH] [v4] net/bnx2x: support 2.5Gbps
Date: Fri, 02 Jun 2023 01:27:55 -0700 (PDT) [thread overview]
Message-ID: <6479a80b.050a0220.8478c.2a60SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/127953
_Functional Testing PASS_
Submitter: Julien Aube <julien_dpdk@jaube.fr>
Date: Friday, June 02 2023 07:57:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:abaa473297cf21cb81e5348185a7694ae2f221e7
127953 --> functional testing pass
Test environment and result as below:
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26507/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-02 8:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 8:27 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 22:27 dpdklab
2023-06-09 22:26 dpdklab
2023-06-09 22:26 dpdklab
2023-06-09 22:23 dpdklab
2023-06-09 22:23 dpdklab
2023-06-09 22:12 dpdklab
2023-06-08 22:04 dpdklab
2023-06-02 9:48 dpdklab
2023-06-02 9:28 dpdklab
2023-06-02 9:18 dpdklab
2023-06-02 9:05 dpdklab
2023-06-02 8:50 dpdklab
2023-06-02 8:49 dpdklab
2023-06-02 8:47 dpdklab
2023-06-02 8:46 dpdklab
2023-06-02 8:35 dpdklab
2023-06-02 8:35 dpdklab
2023-06-02 8:34 dpdklab
2023-06-02 8:34 dpdklab
2023-06-02 8:28 dpdklab
[not found] <20230602075745.6790-1-julien_dpdk@jaube.fr>
2023-06-02 7:55 ` |SUCCESS| pw127953 [PATCH v4] " qemudev
2023-06-02 7:59 ` qemudev
2023-06-02 19:20 ` 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=6479a80b.050a0220.8478c.2a60SMTPIN_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).