From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw98813 [PATCH] crypto/mlx5: fix indirect mkey cleaning
Date: Tue, 14 Sep 2021 09:34:47 -0400 (EDT) [thread overview]
Message-ID: <20210914133447.265D13055F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
Test-Label: iol-aarch64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/98813
_Testing PASS_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Monday, September 13 2021 19:16:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:962bbb0b7f56ab982d6337c9bae05e1b105f8bdd
98813 --> testing pass
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM cross-compilation | PASS |
+------------------------------------+--------------------+
Ubuntu 20.04 ARM cross-compilation
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/18723/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-09-14 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 13:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-18 12:49 dpdklab
2021-09-14 2:11 dpdklab
2021-09-14 1:52 dpdklab
2021-09-14 1:35 dpdklab
2021-09-13 23:43 dpdklab
2021-09-13 21:14 dpdklab
[not found] <20210913191646.612617-1-michaelba@nvidia.com>
2021-09-13 19:18 ` checkpatch
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=20210914133447.265D13055F@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@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).