From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126123 [PATCH] [v3] dmadev: add tracepoints
Date: Sat, 15 Apr 2023 12:52:51 +0000 (UTC) [thread overview]
Message-ID: <20230415125251.BD03760095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126123
_Testing PASS_
Submitter: fengchengwen <fengchengwen@huawei.com>
Date: Saturday, April 15 2023 00:33:22
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
126123 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26006/
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-15 12:52 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 12:52 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-18 15:32 dpdklab
2023-04-15 12:53 dpdklab
2023-04-15 12:20 dpdklab
2023-04-15 12:19 dpdklab
2023-04-15 9:47 dpdklab
2023-04-15 9:06 dpdklab
2023-04-15 8:56 dpdklab
2023-04-15 8:16 dpdklab
2023-04-15 7:52 dpdklab
2023-04-15 7:32 dpdklab
2023-04-15 7:27 dpdklab
2023-04-15 7:22 dpdklab
2023-04-15 7:07 dpdklab
2023-04-15 3:34 dpdklab
2023-04-15 3:21 dpdklab
2023-04-15 3:16 dpdklab
2023-04-15 3:13 dpdklab
2023-04-15 3:05 dpdklab
2023-04-15 3:04 dpdklab
2023-04-15 3:02 dpdklab
2023-04-15 3:01 dpdklab
2023-04-15 3:00 dpdklab
2023-04-15 2:55 dpdklab
2023-04-15 2:41 dpdklab
2023-04-15 2:38 dpdklab
2023-04-15 2:36 dpdklab
2023-04-15 2:34 dpdklab
2023-04-15 2:23 dpdklab
2023-04-15 2:22 dpdklab
2023-04-15 2:22 dpdklab
2023-04-15 2:20 dpdklab
2023-04-15 2:20 dpdklab
2023-04-15 2:19 dpdklab
2023-04-15 2:16 dpdklab
2023-04-15 2:15 dpdklab
2023-04-15 2:12 dpdklab
2023-04-15 2:11 dpdklab
2023-04-15 2:10 dpdklab
2023-04-15 2:07 dpdklab
2023-04-15 2:07 dpdklab
2023-04-15 1:57 dpdklab
2023-04-15 1:56 dpdklab
2023-04-15 1:55 dpdklab
2023-04-15 1:54 dpdklab
2023-04-15 1:53 dpdklab
2023-04-15 1:52 dpdklab
2023-04-15 1:48 dpdklab
2023-04-15 1:46 dpdklab
2023-04-15 1:43 dpdklab
2023-04-15 1:41 dpdklab
2023-04-15 1:41 dpdklab
2023-04-15 1:40 dpdklab
2023-04-15 1:39 dpdklab
2023-04-15 1:38 dpdklab
2023-04-15 1:37 dpdklab
2023-04-15 1:34 dpdklab
2023-04-15 1:33 dpdklab
[not found] <20230415003322.29814-1-fengchengwen@huawei.com>
2023-04-15 0:32 ` |SUCCESS| pw126123 [PATCH v3] " qemudev
2023-04-15 0:36 ` qemudev
2023-04-15 1: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=20230415125251.BD03760095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--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).