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| pw106236 [PATCH] [v2] devtools/cocci: update cocci for ethdev namespace
Date: Sun, 23 Jan 2022 13:20:38 -0500 (EST) [thread overview]
Message-ID: <20220123182038.8EE5F19DD3@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/106236
_Functional Testing PASS_
Submitter: Aman Singh <aman.deep.singh@intel.com>
Date: Sunday, January 23 2022 17:20:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8a5a91401dc23ddab1ddea3667a17a615a25077f
106236 --> 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/20774/
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-23 18:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 18:20 dpdklab [this message]
[not found] <20220123172046.1296964-1-aman.deep.singh@intel.com>
2022-01-23 19:19 ` |SUCCESS| pw106236 [PATCH v2] " 0-day Robot
-- strict thread matches above, loose matches on Subject: below --
2022-01-23 18:56 |SUCCESS| pw106236 [PATCH] [v2] " dpdklab
2022-01-23 18:49 dpdklab
2022-01-23 18:48 dpdklab
2022-01-23 18:45 dpdklab
2022-01-23 18:43 dpdklab
2022-01-23 18:25 dpdklab
2022-01-23 18:23 dpdklab
2022-01-23 18:19 dpdklab
2022-01-23 18:19 dpdklab
2022-01-23 18:15 dpdklab
2022-01-23 18:12 dpdklab
2022-01-23 18:10 dpdklab
2022-01-23 18:06 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=20220123182038.8EE5F19DD3@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).