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
Subject: [dpdk-test-report] |SUCCESS| pw84438 [PATCH] [v3] net/mlx5: check the reg available for metadata action
Date: Fri, 20 Nov 2020 17:38:08 -0500 (EST) [thread overview]
Message-ID: <20201120223808.D06AF88FE7@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/84438
_Functional Testing PASS_
Submitter: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date: Friday, November 20 2020 14:48:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2069f9eefca06190377bbff14734e2326439df42
84438 --> functional testing pass
Test environment and result as below:
Ubuntu 18.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/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/14599/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-11-20 22:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 22:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-21 3:28 dpdklab
2020-11-20 22:59 dpdklab
2020-11-20 22:47 dpdklab
2020-11-20 22:31 dpdklab
[not found] <1605883683-11576-1-git-send-email-viacheslavo@nvidia.com>
2020-11-20 14:48 ` [dpdk-test-report] |SUCCESS| pw84438 [PATCH v3] " checkpatch
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=20201120223808.D06AF88FE7@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--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).