automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Brian Dooley <brian.dooley@intel.com>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132605 [PATCH] [v1] doc: update QAT kernel module entry
Date: Fri, 13 Oct 2023 05:01:35 -0700 (PDT)	[thread overview]
Message-ID: <6529319f.050a0220.5cfbe.362dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132605

_Testing PASS_

Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Friday, October 13 2023 10:59:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:77f913752a55c0262bfda99a1b69ca0bd804c6c7

132605 --> testing pass

Test environment and result as below:

+-----------------+---------------------------+
|   Environment   | cryptodev_sw_zuc_autotest |
+=================+===========================+
| Debian 11 (arm) | PASS                      |
+-----------------+---------------------------+


Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-13 12:01 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 12:01 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-13 13:13 dpdklab
2023-10-13 13:13 dpdklab
2023-10-13 13:09 dpdklab
2023-10-13 13:06 dpdklab
2023-10-13 13:02 dpdklab
2023-10-13 12:59 dpdklab
2023-10-13 12:58 dpdklab
2023-10-13 12:57 dpdklab
2023-10-13 12:51 dpdklab
2023-10-13 12:48 dpdklab
2023-10-13 12:47 dpdklab
2023-10-13 12:43 dpdklab
2023-10-13 12:40 dpdklab
2023-10-13 12:37 dpdklab
2023-10-13 12:35 dpdklab
2023-10-13 12:30 dpdklab
2023-10-13 12:30 dpdklab
2023-10-13 12:28 dpdklab
2023-10-13 12:28 dpdklab
2023-10-13 12:24 dpdklab
     [not found] <20231013105930.893575-1-brian.dooley@intel.com>
2023-10-13 10:40 ` |SUCCESS| pw132605 [PATCH v1] " qemudev
2023-10-13 10:44 ` qemudev
2023-10-13 11:00 ` checkpatch
2023-10-13 12:19 ` 0-day Robot
2023-10-13 12:17 |SUCCESS| pw132605 [PATCH] [v1] " dpdklab
2023-10-13 12:16 dpdklab
2023-10-13 12:16 dpdklab
2023-10-13 12:15 dpdklab
2023-10-13 12:07 dpdklab
2023-10-13 12:07 dpdklab
2023-10-13 12:07 dpdklab
2023-10-13 12:05 dpdklab
2023-10-13 12:04 dpdklab
2023-10-13 12:03 dpdklab
2023-10-13 12:03 dpdklab
2023-10-13 12:03 dpdklab
2023-10-13 12:02 dpdklab
2023-10-13 12:02 dpdklab
2023-10-13 12:02 dpdklab
2023-10-13 12:02 dpdklab
2023-10-13 12:02 dpdklab
2023-10-13 12:01 dpdklab
2023-10-13 12:01 dpdklab
2023-10-13 12:00 dpdklab
2023-10-13 12:00 dpdklab
2023-10-13 12:00 dpdklab
2023-10-13 11:59 dpdklab
2023-10-13 11:59 dpdklab
2023-10-13 11:59 dpdklab
2023-10-13 11:59 dpdklab
2023-10-13 11:58 dpdklab
2023-10-13 11:51 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=6529319f.050a0220.5cfbe.362dSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=brian.dooley@intel.com \
    --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).