From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134188 [PATCH] raw/cnxk_bphy: switch to dynamic logging
Date: Tue, 14 Nov 2023 02:09:57 -0800 (PST) [thread overview]
Message-ID: <65534775.2e0a0220.48710.5005SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/134188
_Functional Testing PASS_
Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Tuesday, November 14 2023 08:04:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:737faa1b4331f6395bc3a665159a489f404e6052
134188 --> 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
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-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/28368/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-14 10:10 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 10:09 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-16 5:03 dpdklab
2023-11-16 4:41 dpdklab
2023-11-14 13:47 dpdklab
2023-11-14 11:33 dpdklab
2023-11-14 10:31 dpdklab
2023-11-14 10:27 dpdklab
2023-11-14 10:22 dpdklab
2023-11-14 10:20 dpdklab
2023-11-14 10:19 dpdklab
2023-11-14 10:18 dpdklab
2023-11-14 10:16 dpdklab
2023-11-14 10:16 dpdklab
2023-11-14 10:15 dpdklab
2023-11-14 10:15 dpdklab
2023-11-14 10:15 dpdklab
2023-11-14 10:15 dpdklab
2023-11-14 10:14 dpdklab
2023-11-14 10:14 dpdklab
2023-11-14 10:14 dpdklab
2023-11-14 10:14 dpdklab
2023-11-14 10:14 dpdklab
2023-11-14 10:14 dpdklab
2023-11-14 10:14 dpdklab
2023-11-14 10:13 dpdklab
2023-11-14 10:13 dpdklab
2023-11-14 10:13 dpdklab
2023-11-14 10:13 dpdklab
2023-11-14 10:12 dpdklab
2023-11-14 10:12 dpdklab
2023-11-14 10:12 dpdklab
2023-11-14 10:12 dpdklab
2023-11-14 10:12 dpdklab
2023-11-14 10:11 dpdklab
2023-11-14 10:11 dpdklab
2023-11-14 10:11 dpdklab
2023-11-14 10:11 dpdklab
2023-11-14 10:11 dpdklab
2023-11-14 10:10 dpdklab
2023-11-14 10:10 dpdklab
2023-11-14 10:10 dpdklab
2023-11-14 10:10 dpdklab
2023-11-14 10:09 dpdklab
2023-11-14 10:09 dpdklab
2023-11-14 10:07 dpdklab
2023-11-14 10:07 dpdklab
2023-11-14 10:07 dpdklab
2023-11-14 10:07 dpdklab
2023-11-14 10:07 dpdklab
2023-11-14 10:07 dpdklab
2023-11-14 10:04 dpdklab
2023-11-14 10:04 dpdklab
2023-11-14 10:04 dpdklab
2023-11-14 10:03 dpdklab
2023-11-14 9:42 dpdklab
[not found] <20231114080446.3574237-1-tduszynski@marvell.com>
2023-11-14 7:45 ` qemudev
2023-11-14 7:49 ` qemudev
2023-11-14 8:05 ` checkpatch
2023-11-14 9:19 ` 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=65534775.2e0a0220.48710.5005SMTPIN_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).