From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
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| pw106831-106832 [PATCH] [v2, 2/2] net/mlx5: remove unused metadata shift parameter
Date: Thu, 3 Feb 2022 17:54:20 -0500 (EST) [thread overview]
Message-ID: <20220203225420.D7144361B@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/106832
_Functional Testing PASS_
Submitter: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date: Thursday, February 03 2022 08:46:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ed579e50c66db90485593c6c79f5366a57145f2a
106831-106832 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/20896/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-02-03 22:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 22:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-03 23:05 dpdklab
2022-02-03 22:53 dpdklab
2022-02-03 22:22 dpdklab
2022-02-03 11:41 dpdklab
2022-02-03 11:29 dpdklab
2022-02-03 11:15 dpdklab
2022-02-03 10:28 dpdklab
2022-02-03 10:16 dpdklab
2022-02-03 10:15 dpdklab
2022-02-03 10:11 dpdklab
2022-02-03 10:11 dpdklab
2022-02-03 10:09 dpdklab
2022-02-03 10:01 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=20220203225420.D7144361B@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--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).