automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137039 [PATCH] doc: fix some typos in cryptodev overview
Date: Fri, 23 Feb 2024 22:48:45 -0800 (PST)	[thread overview]
Message-ID: <65d9914d.050a0220.69be7.10dcSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137039

_Functional Testing PASS_

Submitter: Andrew Boyer <Andrew.Boyer@amd.com>
Date: Thursday, February 22 2024 17:41:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137039 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29227/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2024-02-24  6:49 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24  6:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-25  1:30 dpdklab
2024-02-25  1:02 dpdklab
2024-02-25  0:43 dpdklab
2024-02-24 13:49 dpdklab
2024-02-24 11:02 dpdklab
2024-02-24  9:15 dpdklab
2024-02-24  9:09 dpdklab
2024-02-24  9:09 dpdklab
2024-02-24  9:08 dpdklab
2024-02-24  8:59 dpdklab
2024-02-24  8:48 dpdklab
2024-02-24  8:45 dpdklab
2024-02-24  8:44 dpdklab
2024-02-24  8:43 dpdklab
2024-02-24  8:42 dpdklab
2024-02-24  8:42 dpdklab
2024-02-24  8:41 dpdklab
2024-02-24  8:40 dpdklab
2024-02-24  8:39 dpdklab
2024-02-24  8:38 dpdklab
2024-02-24  8:37 dpdklab
2024-02-24  8:34 dpdklab
2024-02-24  8:30 dpdklab
2024-02-24  8:26 dpdklab
2024-02-24  8:26 dpdklab
2024-02-24  8:25 dpdklab
2024-02-24  8:24 dpdklab
2024-02-24  8:23 dpdklab
2024-02-24  8:22 dpdklab
2024-02-24  8:22 dpdklab
2024-02-24  8:21 dpdklab
2024-02-24  8:20 dpdklab
2024-02-24  8:19 dpdklab
2024-02-24  8:19 dpdklab
2024-02-24  8:17 dpdklab
2024-02-24  8:17 dpdklab
2024-02-24  8:15 dpdklab
2024-02-24  8:14 dpdklab
2024-02-24  8:14 dpdklab
2024-02-24  8:13 dpdklab
2024-02-24  8:13 dpdklab
2024-02-24  8:12 dpdklab
2024-02-24  8:05 dpdklab
2024-02-24  8:04 dpdklab
2024-02-24  8:03 dpdklab
2024-02-24  7:58 dpdklab
2024-02-24  7:57 dpdklab
2024-02-24  7:56 dpdklab
2024-02-24  7:56 dpdklab
2024-02-24  7:55 dpdklab
2024-02-24  7:49 dpdklab
2024-02-24  7:49 dpdklab
2024-02-24  7:47 dpdklab
2024-02-24  7:45 dpdklab
2024-02-24  7:40 dpdklab
2024-02-24  7:39 dpdklab
2024-02-24  7:39 dpdklab
2024-02-24  7:18 dpdklab
2024-02-24  6:45 dpdklab
2024-02-24  6:43 dpdklab
2024-02-24  6:24 dpdklab
2024-02-24  6:23 dpdklab
2024-02-24  6:22 dpdklab
2024-02-24  6:22 dpdklab
2024-02-24  6:21 dpdklab
2024-02-24  6:13 dpdklab
2024-02-24  6:07 dpdklab
2024-02-24  6:04 dpdklab
     [not found] <20240222174111.25007-1-andrew.boyer@amd.com>
2024-02-22 17:18 ` qemudev
2024-02-22 17:23 ` qemudev
2024-02-22 17:42 ` checkpatch
2024-02-22 18:44 ` 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=65d9914d.050a0220.69be7.10dcSMTPIN_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).