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: |SUCCESS| pw106124 [PATCH] [v2] net/enic: support GENEVE flow item
Date: Thu, 20 Jan 2022 10:06:54 -0500 (EST) [thread overview]
Message-ID: <20220120150654.E78571AE@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/106124
_Functional Testing PASS_
Submitter: Hyong Youb Kim <hyonkim@cisco.com>
Date: Thursday, January 20 2022 14:26:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:62c21c38a26e654bba09be147ea2d61c2e699a13
106124 --> 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/20746/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-01-20 15:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 15:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-21 4:23 dpdklab
2022-01-20 20:28 dpdklab
2022-01-20 17:05 dpdklab
2022-01-20 16:45 dpdklab
2022-01-20 16:44 dpdklab
2022-01-20 16:36 dpdklab
2022-01-20 16:29 dpdklab
[not found] <20220120142637.16980-1-hyonkim@cisco.com>
2022-01-20 14:28 ` |SUCCESS| pw106124 [PATCH v2] " checkpatch
2022-01-20 16:19 ` 0-day Robot
2022-01-20 15:40 |SUCCESS| pw106124 [PATCH] [v2] " dpdklab
2022-01-20 15:36 dpdklab
2022-01-20 15:18 dpdklab
2022-01-20 15:11 dpdklab
2022-01-20 15:07 dpdklab
2022-01-20 14:56 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=20220120150654.E78571AE@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).