From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126099 [PATCH] [v2] kni: fix build with Linux 6.3
Date: Fri, 14 Apr 2023 17:47:18 +0000 (UTC) [thread overview]
Message-ID: <20230414174718.9C67D6008C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/126099
_Functional Testing PASS_
Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Friday, April 14 2023 15:25:22
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
126099 --> 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/26004/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-14 17:47 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 17:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-15 7:52 dpdklab
2023-04-15 7:52 dpdklab
2023-04-15 7:08 dpdklab
2023-04-15 7:08 dpdklab
2023-04-15 4:06 dpdklab
2023-04-15 4:01 dpdklab
2023-04-15 3:57 dpdklab
2023-04-15 3:41 dpdklab
2023-04-15 3:36 dpdklab
2023-04-15 3:32 dpdklab
2023-04-15 2:42 dpdklab
2023-04-15 2:03 dpdklab
2023-04-15 0:06 dpdklab
2023-04-14 22:40 dpdklab
2023-04-14 20:50 dpdklab
2023-04-14 20:19 dpdklab
2023-04-14 20:16 dpdklab
2023-04-14 20:15 dpdklab
2023-04-14 20:12 dpdklab
2023-04-14 20:12 dpdklab
2023-04-14 20:09 dpdklab
2023-04-14 19:58 dpdklab
2023-04-14 19:41 dpdklab
2023-04-14 19:40 dpdklab
2023-04-14 19:40 dpdklab
2023-04-14 19:39 dpdklab
2023-04-14 19:37 dpdklab
2023-04-14 19:35 dpdklab
2023-04-14 19:34 dpdklab
2023-04-14 19:32 dpdklab
2023-04-14 19:31 dpdklab
2023-04-14 19:28 dpdklab
2023-04-14 19:26 dpdklab
2023-04-14 19:20 dpdklab
2023-04-14 19:04 dpdklab
2023-04-14 18:57 dpdklab
2023-04-14 18:50 dpdklab
2023-04-14 18:44 dpdklab
2023-04-14 18:41 dpdklab
2023-04-14 18:39 dpdklab
2023-04-14 18:33 dpdklab
2023-04-14 18:32 dpdklab
2023-04-14 18:28 dpdklab
2023-04-14 18:26 dpdklab
2023-04-14 18:25 dpdklab
2023-04-14 18:20 dpdklab
2023-04-14 18:19 dpdklab
2023-04-14 18:13 dpdklab
2023-04-14 18:04 dpdklab
2023-04-14 18:01 dpdklab
2023-04-14 17:52 dpdklab
2023-04-14 17:52 dpdklab
2023-04-14 17:48 dpdklab
2023-04-14 17:45 dpdklab
2023-04-14 17:44 dpdklab
2023-04-14 17:43 dpdklab
2023-04-14 17:39 dpdklab
[not found] <20230414152522.83636-1-ferruh.yigit@amd.com>
2023-04-14 15:17 ` |SUCCESS| pw126099 [PATCH v2] " qemudev
2023-04-14 15:21 ` qemudev
2023-04-14 15:27 ` checkpatch
2023-04-14 16:39 ` 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=20230414174718.9C67D6008C@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).