From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134427 [PATCH] net/txgbe: fix out of bound access
Date: Thu, 16 Nov 2023 09:06:29 -0800 (PST) [thread overview]
Message-ID: <65564c15.170a0220.dd415.30afSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/134427
_Functional Testing PASS_
Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Thursday, November 16 2023 14:07:18
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92d7ce4afc4a558f27bbc8368823c625f4e0f9dc
134427 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28399/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-16 17:06 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 17:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-17 7:45 dpdklab
2023-11-17 7:24 dpdklab
2023-11-16 20:13 dpdklab
2023-11-16 18:11 dpdklab
2023-11-16 17:42 dpdklab
2023-11-16 17:29 dpdklab
2023-11-16 17:27 dpdklab
2023-11-16 17:26 dpdklab
2023-11-16 17:23 dpdklab
2023-11-16 17:21 dpdklab
2023-11-16 17:20 dpdklab
2023-11-16 17:19 dpdklab
2023-11-16 17:18 dpdklab
2023-11-16 17:17 dpdklab
2023-11-16 17:17 dpdklab
2023-11-16 17:16 dpdklab
2023-11-16 17:15 dpdklab
2023-11-16 17:15 dpdklab
2023-11-16 17:15 dpdklab
2023-11-16 17:14 dpdklab
2023-11-16 17:14 dpdklab
2023-11-16 17:14 dpdklab
2023-11-16 17:14 dpdklab
2023-11-16 17:13 dpdklab
2023-11-16 17:13 dpdklab
2023-11-16 17:13 dpdklab
2023-11-16 17:13 dpdklab
2023-11-16 17:13 dpdklab
2023-11-16 17:12 dpdklab
2023-11-16 17:12 dpdklab
2023-11-16 17:11 dpdklab
2023-11-16 17:10 dpdklab
2023-11-16 17:10 dpdklab
2023-11-16 17:09 dpdklab
2023-11-16 17:09 dpdklab
2023-11-16 17:08 dpdklab
2023-11-16 17:08 dpdklab
2023-11-16 17:08 dpdklab
2023-11-16 17:08 dpdklab
2023-11-16 17:07 dpdklab
2023-11-16 17:07 dpdklab
2023-11-16 17:07 dpdklab
2023-11-16 17:07 dpdklab
2023-11-16 17:07 dpdklab
2023-11-16 17:06 dpdklab
2023-11-16 17:06 dpdklab
2023-11-16 17:05 dpdklab
2023-11-16 17:04 dpdklab
2023-11-16 17:04 dpdklab
2023-11-16 17:03 dpdklab
2023-11-16 17:03 dpdklab
2023-11-16 17:02 dpdklab
2023-11-16 17:02 dpdklab
[not found] <20231116140718.4026676-1-ferruh.yigit@amd.com>
2023-11-16 13:48 ` qemudev
2023-11-16 13:53 ` qemudev
2023-11-16 14:59 ` 0-day Robot
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=65564c15.170a0220.dd415.30afSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).