From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124027 [PATCH] [v1] net/mlx5: enable hint in async table
Date: Thu, 16 Feb 2023 01:24:14 -0500 (EST) [thread overview]
Message-ID: <20230216062414.B6D064AC@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124027
_Functional Testing PASS_
Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Thursday, February 16 2023 05:49:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:01314192b7856d3737eb6d80aa351f60a07631af
124027 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25416/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-16 6:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 6:24 dpdklab [this message]
2023-02-16 6:29 dpdklab
2023-02-16 6:35 dpdklab
2023-02-16 6:35 dpdklab
2023-02-16 6:39 dpdklab
2023-02-16 6:49 dpdklab
2023-02-16 7:38 dpdklab
[not found] <20230216054923.3973237-1-rongweil@nvidia.com>
2023-02-16 5:38 ` |SUCCESS| pw124027 [PATCH v1] " qemudev
2023-02-16 5:42 ` qemudev
2023-02-16 5:50 ` checkpatch
2023-02-16 7:59 ` 0-day Robot
2023-02-17 13:28 |SUCCESS| pw124027 [PATCH] [v1] " dpdklab
2023-02-19 3:55 dpdklab
2023-02-23 2:13 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=20230216062414.B6D064AC@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).