From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137809 [PATCH] rte_memcpy: fix off by one for size 16 an
Date: Sat, 02 Mar 2024 13:55:02 -0800 (PST) [thread overview]
Message-ID: <65e3a036.c80a0220.84812.e66dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240302204923.227105-1-stephen@networkplumber.org>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137809
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Saturday, March 02 2024 20:49:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5df34de5808a7b826b8bc035d6ee3161a12be364
137809 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29387/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-02 21:55 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240302204923.227105-1-stephen@networkplumber.org>
2024-03-02 20:27 ` |SUCCESS| pw137809 [PATCH] rte_memcpy: fix off by one for size 16 and 32 qemudev
2024-03-02 20:31 ` qemudev
2024-03-02 20:51 ` checkpatch
2024-03-02 21:44 ` 0-day Robot
2024-03-02 21:48 ` |SUCCESS| pw137809 [PATCH] rte_memcpy: fix off by one for size 16 an dpdklab
2024-03-02 21:49 ` dpdklab
2024-03-02 21:49 ` dpdklab
2024-03-02 21:50 ` dpdklab
2024-03-02 21:50 ` dpdklab
2024-03-02 21:51 ` dpdklab
2024-03-02 21:51 ` dpdklab
2024-03-02 21:51 ` dpdklab
2024-03-02 21:51 ` dpdklab
2024-03-02 21:51 ` dpdklab
2024-03-02 21:52 ` dpdklab
2024-03-02 21:53 ` dpdklab
2024-03-02 21:54 ` dpdklab
2024-03-02 21:54 ` dpdklab
2024-03-02 21:55 ` dpdklab [this message]
2024-03-02 21:55 ` dpdklab
2024-03-02 21:57 ` dpdklab
2024-03-02 21:57 ` dpdklab
2024-03-02 21:59 ` dpdklab
2024-03-02 21:59 ` dpdklab
2024-03-02 21:59 ` dpdklab
2024-03-02 22:01 ` dpdklab
2024-03-02 22:01 ` dpdklab
2024-03-02 22:02 ` dpdklab
2024-03-02 22:02 ` dpdklab
2024-03-02 22:02 ` dpdklab
2024-03-02 22:03 ` dpdklab
2024-03-02 22:04 ` dpdklab
2024-03-02 22:04 ` dpdklab
2024-03-02 22:05 ` dpdklab
2024-03-02 22:05 ` dpdklab
2024-03-02 22:05 ` dpdklab
2024-03-02 22:06 ` dpdklab
2024-03-02 22:06 ` dpdklab
2024-03-02 22:06 ` dpdklab
2024-03-02 22:07 ` dpdklab
2024-03-02 22:07 ` dpdklab
2024-03-02 22:08 ` dpdklab
2024-03-02 22:08 ` dpdklab
2024-03-02 22:09 ` dpdklab
2024-03-02 22:09 ` dpdklab
2024-03-02 22:09 ` dpdklab
2024-03-02 22:12 ` dpdklab
2024-03-02 22:16 ` dpdklab
2024-03-02 22:17 ` dpdklab
2024-03-02 22:18 ` dpdklab
2024-03-02 22:18 ` dpdklab
2024-03-02 22:18 ` dpdklab
2024-03-02 22:19 ` dpdklab
2024-03-02 22:19 ` dpdklab
2024-03-02 22:20 ` dpdklab
2024-03-02 22:22 ` dpdklab
2024-03-02 22:24 ` dpdklab
2024-03-02 22:24 ` dpdklab
2024-03-02 22:24 ` dpdklab
2024-03-02 22:26 ` dpdklab
2024-03-02 22:28 ` dpdklab
2024-03-02 22:31 ` dpdklab
2024-03-02 22:32 ` dpdklab
2024-03-02 22:32 ` dpdklab
2024-03-02 22:34 ` dpdklab
2024-03-02 22:35 ` dpdklab
2024-03-02 22:42 ` dpdklab
2024-03-02 22:49 ` dpdklab
2024-03-02 23:11 ` dpdklab
2024-03-03 7:01 ` dpdklab
2024-03-06 17:41 ` dpdklab
2024-03-06 18:13 ` dpdklab
2024-03-06 18:44 ` 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=65e3a036.c80a0220.84812.e66dSMTPIN_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).